| 2 |
Approval of Agenda |
|
| R1-2308800 |
Draft Agenda of RAN1#114bis meeting |
RAN1 Chair |
| R1-2308803 |
RAN1#114bis Meeting Timelines, Scope, Process |
RAN1 Chair, ETSI MCC |
| R1-2308804 |
RAN1#114bis Meeting Management |
RAN1 Chair |
| 3 |
Highlights from RAN plenary |
|
| R1-2308801 |
Highlights from RAN#101 |
RAN1 Chair |
| 4 |
Approval of Minutes from previous meetings |
|
| R1-2308802 |
Report of RAN1#114 meeting |
ETSI MCC |
| 5 |
Incoming Liaison Statements |
|
| R1-2308805 |
Response LS to RAN WG2 on reporting positioning measurements taken in RRC_IDLE |
SA2, CATT |
| R1-2308806 |
LS on report quantity parameter setting for CQI reporting with 1Tx |
RAN4, Anritsu |
| R1-2308807 |
Reply LS to RAN1 on TDCP Measurements |
RAN4, Apple |
| R1-2308808 |
Reply LS on single measurement gap for DL PRS with Rx Hopping |
RAN4, xiaomi |
| R1-2308809 |
Reply LS on determination of UL timing to transmit SRS for positioning by UEs in RRC_INACTIVE states |
RAN4, CMCC |
| R1-2308810 |
Reply LS on PDCCH order RACH on neighbour cell |
RAN4, CATT |
| R1-2308811 |
Reply LS on beam application time and UE based TA measurement for LTM |
RAN4, Ericsson |
| R1-2308812 |
Reply LS on monitoring of paging occasions for CG-SDT with HD-FDD Redcap UEs |
RAN4, MediaTek |
| R1-2308813 |
LS on Dual TCI state switching in mDCI |
RAN4, Ericsson |
| R1-2308814 |
LS on power scaling and PHR in 38.213 |
RAN4, vivo |
| R1-2308815 |
LS on enhancements to realize increasing UE power high limit for CA and DC |
RAN4, Nokia |
| R1-2308816 |
Reply LS on on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs |
RAN4, CATT |
| R1-2308817 |
Reply LS to RAN1 on low-power wake-up receiver architectures |
RAN4, vivo |
| R1-2308818 |
LS on FR2 SCell activation enhancements |
RAN4, Apple |
| R1-2308819 |
LS on NR SL unlicensed LBT failures UE behavior |
RAN4, Ericsson |
| R1-2308820 |
LS on SL positioning and CPP measurements report mapping |
RAN4, CATT |
| R1-2308821 |
Reply LS on LPHAP |
RAN4, Huawei |
| R1-2308822 |
Reply LS on new DRX cycles in rational numbers |
RAN4, Nokia |
| R1-2308823 |
LS on NR ATG network assistance and TA reporting |
RAN4, CMCC |
| R1-2308824 |
Reply LS on NPDCCH monitoring restriction for NB-IoT NTN |
RAN2, Lenovo |
| R1-2308825 |
Reply LS on XR capacity enhancements |
RAN2, MediaTek |
| R1-2308826 |
LS on the support of multiple location estimate instances in a single measurement report |
RAN2, ZTE |
| R1-2308827 |
Reply LS on SRS bandwidth aggregation for positioning |
RAN2, ZTE |
| R1-2308828 |
On frequencyInfo for NR SL RSRP measurements |
RAN2, Huawei |
| R1-2308829 |
Reply LS on beam application time for LTM |
RAN2, Fujitsu, MediaTek, CATT |
| R1-2308830 |
Reply LS to RAN1 on Msg4 PDSCH transmission to Rel-18 eRedCap UEs |
RAN2, vivo |
| R1-2308831 |
On miscellaneous corrections on TR 37.985 |
RAN2, Huawei |
| R1-2308832 |
LS on SL RB set index and LBT failure indication for PSFCH |
RAN2, CATT |
| R1-2308833 |
LS on RAN2 progress on LTM |
RAN2, Huawei |
| R1-2308834 |
LS on SL positioning MAC agreements |
RAN2, Huawei |
| R1-2308835 |
Reply LS on Approaches during execution for inter-DU LTM |
RAN2, Ericsson |
| R1-2308836 |
Reply LS to SA2 on Sidelink positioning procedure |
RAN2, xiaomi |
| R1-2308910 |
Further discussion on LS for RACH-less handover |
Huawei, HiSilicon |
| R1-2308947 |
Discussion on RAN2 LS of Data Collection Requirements |
Ericsson Inc. |
| R1-2308972 |
Discussion on LS on SL positioning MAC agreements |
Spreadtrum Communications |
| R1-2309024 |
Discussion on required DCI signalling for advanced receiver on MU-MIMO scenario |
ZTE |
| R1-2309025 |
Draft reply LS on report quantity parameter setting for CQI reporting with 1Tx |
ZTE |
| R1-2309026 |
Draft reply LS on power scaling and PHR in 38.213 |
ZTE |
| R1-2309031 |
Discussion on collision handling between paging occasions and CG SDT for HD-FDD UEs |
vivo |
| R1-2309032 |
Draft reply LS on monitoring of paging occasions for CG-SDT with HD-FDD Redcap UEs |
vivo |
| R1-2309033 |
Draft reply LS on XR capacity enhancement |
vivo |
| R1-2309034 |
Draft LS reply to frequencyInfo for NR SL RSRP measurements |
vivo |
| R1-2309035 |
Discussion on frequencyInfo for NR SL RSRP measurements |
vivo |
| R1-2309036 |
Draft LS reply on RB set index |
vivo |
| R1-2309037 |
Draft LS reply on the support of multiple location estimate instances in a single measurement report |
vivo |
| R1-2309038 |
Draft LS reply on SL positioning MAC agreements |
vivo |
| R1-2309039 |
Draft LS reply on enhancements to realize increasing UE power high limit for CA and DC |
vivo |
| R1-2309040 |
Discussions on RAN2 LS on RACH-less Handover |
vivo |
| R1-2309041 |
Discussion of the LS on the system parameters for NTN above 10 GHz |
vivo |
| R1-2309042 |
Draft reply LS on report quantity parameter setting for CQI reporting with 1Tx |
vivo |
| R1-2309043 |
Draft reply LS on dual TCI state switching in mDCI |
vivo |
| R1-2309044 |
Discussion on power scaling and PHR in 38.213 |
vivo |
| R1-2309045 |
Draft reply LS on power scaling and PHR in 38.213 |
vivo |
| R1-2309046 |
Discussion on CSS for multicast reception in RRC_INACTIVE |
vivo |
| R1-2309047 |
Discussion on beam application time for L1/L2-Triggered Mobility |
vivo |
| R1-2309117 |
About LS on NR SL unlicensed LBT failures UE behaviour |
ZTE, Sanechips |
| R1-2309118 |
About LS on frequencyInfo for NR SL RSRP measurements |
ZTE, Sanechips, CAICT |
| R1-2309119 |
About LS on SL RB set index and LBT failure indication for PSFCH |
ZTE, Sanechips, CAICT |
| R1-2309120 |
[Draft] Reply LS on enhancements to realize increasing UE power high limit for CA and DC |
ZTE |
| R1-2309145 |
Discussion on reply LS on paging overlapping with CG-SDT for HD-FDD RedCap UE |
ZTE |
| R1-2309146 |
Draft reply LS on paging and CG-SDT conflicting issue for HD-FDD RedCap UE |
ZTE |
| R1-2309170 |
Draft reply LS on report quantity parameter setting for CQI reporting with 1Tx |
LG Electronics |
| R1-2309173 |
Draft reply LS on XR capacity enhancement |
ZTE, Sanechips |
| R1-2309193 |
Draft Reply LS on SL positioning MAC agreements |
Intel Coporation |
| R1-2309212 |
Discussion on RAN4 LS on report quantity parameter settings for CQI reporting with 1Tx |
Ericsson |
| R1-2309217 |
Draft reply LS on SL positioning MAC agreements |
ZTE |
| R1-2309218 |
Draft reply LS on support of multiple location estimate instances in a single measurement |
ZTE |
| R1-2309232 |
Discussion on LS on frequencyInfo for NR SL RSRP measurements |
LG Electronics |
| R1-2309233 |
Discussion on LS on SL RB set index and LBT failure indication for PSFCH |
LG Electronics |
| R1-2309234 |
Discussion on LS on NR SL unlicensed LBT failures UE behavior |
LG Electronics |
| R1-2309265 |
draft reply LS on Dual TCI switching |
Google |
| R1-2309266 |
draft Reply LS on power scaling and PHR |
Google |
| R1-2309298 |
Discussion on reply LS on XR capacity enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2309324 |
Draft reply LS on dual TCI state switching in mDCI |
Lenovo |
| R1-2309325 |
Draft reply LS on power scaling and PHR in 38.213 |
Lenovo |
| R1-2309338 |
Draft reply LS on report quantity parameter setting for CQI reporting with 1Tx |
Samsung |
| R1-2309339 |
Draft reply LS on Dual TCI state switching in mDCI |
Samsung |
| R1-2309340 |
Draft reply LS on SL RB set index and LBT failure indication for PSFCH |
Samsung |
| R1-2309341 |
Discussion on RAN2 LS on RACH-less handover |
Samsung |
| R1-2309342 |
Discussion on RAN4 LS on system parameters for NTN above 10 GHz |
Samsung |
| R1-2309343 |
Draft reply LS on beam application time for LTM |
Samsung |
| R1-2309344 |
Draft reply LS on the support of multiple location estimate instances in a single measurement report |
Samsung |
| R1-2309345 |
Discussion on multiple location estimate instances |
Samsung |
| R1-2309346 |
Draft reply LS on SL positioning MAC agreements |
Samsung |
| R1-2309347 |
Draft reply LS on frequencyInfo for NR SL RSRP measurements |
Samsung |
| R1-2309348 |
Draft reply LS on power scaling and PHR in 38.213 |
Samsung |
| R1-2309417 |
Discussion on RAN2 LS on Data Collection Requirements for AI/ML operation |
xiaomi |
| R1-2309418 |
Discussions on RAN2 LS on SL positioning MAC agreements |
xiaomi |
| R1-2309419 |
[Draft] Reply LS on SL RB set index and LBT failure indication for PSFCH |
xiaomi |
| R1-2309420 |
[Draft] Reply LS on XR capacity enhancements |
xiaomi |
| R1-2309468 |
Discussion on LS from RAN2 on SL RB set index and LBT failure indication for PSFCH |
CATT, CICTCI |
| R1-2309469 |
Draft reply LS on SL RB set index and LBT failure indication for PSFCH |
CATT, CICTCI |
| R1-2309470 |
Draft reply LS on frequencyInfo for NR SL RSRP measurements |
CATT, CICTCI |
| R1-2309471 |
Draft reply LS on power scaling and PHR in 38.213 |
CATT |
| R1-2309472 |
Draft reply LS on report quantity parameter setting for CQI reporting with 1Tx |
CATT |
| R1-2309473 |
Discussion on multicast reception in RRC_INACTIVE |
CATT, CBN |
| R1-2309474 |
Discussion on the support of multiple location estimate instances in a single measurement report |
CATT |
| R1-2309475 |
Draft reply LS on the support of multiple location estimate instances in a single measurement report |
CATT |
| R1-2309476 |
Discussion on SL positioning MAC agreements |
CATT |
| R1-2309477 |
Draft reply LS on SL positioning MAC agreements |
CATT |
| R1-2309573 |
Discussion on LS on Dual TCI state switching in mDCI |
OPPO |
| R1-2309574 |
Discussion on LS on power scaling and PHR in 38.213 |
OPPO |
| R1-2309582 |
Discussion on Reply LS on beam application time for LTM |
OPPO |
| R1-2309583 |
Draft reply LS on frequencyInfo for NR SL RSRP measurements |
OPPO |
| R1-2309584 |
Discussion on SL RB set index |
OPPO |
| R1-2309585 |
Draft reply LS on SL RB set index and LBT failure indication for PSFCH |
OPPO |
| R1-2309594 |
Discussion on the LS from RAN2 on Sidelink positioning MAC agreements |
OPPO |
| R1-2309595 |
Draft reply LS to RAN2 on Sidelink positioning MAC agreements |
OPPO |
| R1-2309610 |
Discussion on remaining issue for RACH less handover for NR NTN |
OPPO |
| R1-2309621 |
Discussion on RAN2 LS for XP capacity enhancement |
OPPO |
| R1-2309654 |
Discussion on LS on multicast reception in RRC_INACTIVE |
CMCC |
| R1-2309655 |
Discussion on LS on XR capacity enhancements |
CMCC |
| R1-2309656 |
Discussion on RAN4 LS on enhancements to realize increasing UE power high limit for CA and DC |
CMCC |
| R1-2309657 |
Discussion on RAN2 LS on SL-PRS priority |
CMCC |
| R1-2309658 |
Discussion on RAN2 LS on data collection |
CMCC |
| R1-2309725 |
Discussion of RAN4 Reply LS on monitoring paging occasions for CG-SDT with HD-FD |
Nokia, Nokia Shanghai Bell |
| R1-2309730 |
Draft reply LS on Dual TCI state switching in mDCI |
ZTE |
| R1-2309735 |
Open issues related to NTN operation in frequency bands above 10 GHz |
Nokia, Nokia Shanghai Bell |
| R1-2309740 |
Discussion on the support of multiple location estimate instances in a single measurement report |
Huawei, HiSilicon |
| R1-2309742 |
Discussion on SL positioning MAC agreements |
Huawei, HiSilicon |
| R1-2309743 |
Draft Reply LS on SL positioning MAC agreements |
Huawei, HiSilicon |
| R1-2309745 |
Discussion on RAN2 LS on frequencyInfo for NR SL RSRP measurements |
Huawei, HiSilicon |
| R1-2309753 |
Discussion on LS on dual TCI state switching in mDCI |
Huawei, HiSilicon |
| R1-2309755 |
Discussion on LS on SL RB set index and LBT failure indication for PSFCH |
Huawei, HiSilicon |
| R1-2309756 |
Discussion on reply LS on XR capacity enhancements |
Huawei, HiSilicon |
| R1-2309803 |
Discussion on LS on Data Collection Requirements and Assumptions |
Google |
| R1-2309807 |
Discussion on multicast reception in RRC_INACTIVE |
Apple |
| R1-2309808 |
Draft Reply LS on RACH-less Handover |
Apple |
| R1-2309809 |
Draft Reply LS on frequencyInfo for NR SL RSRP Measurements |
Apple |
| R1-2309810 |
Discussion on RAN2 LS on SL RB Set Index and LBT Failure Indication for PSFCH |
Apple |
| R1-2309811 |
Draft Reply LS on SL RB Set Index and LBT Failure Inidcation for PSFCH |
Apple |
| R1-2309812 |
Draft reply LS on Data Collection Requirements and Assumptions Part B |
Apple |
| R1-2309813 |
Discussion on RAN4 LS on Dual TCI state switching in mDCI |
Apple |
| R1-2309814 |
Draft Reply LS on power scaling and PHR in 38.213 |
Apple |
| R1-2309871 |
Discussion on reply LS on PartB of data collection requirements and assumptions |
vivo |
| R1-2309927 |
Discussion on multicast reception in RRC_INACTIVE |
Nokia, Nokia Shanghai Bell |
| R1-2309957 |
Draft Reply LS on Dual TCI state switching in mDCI |
Apple Inc. |
| R1-2309993 |
Discussion on RAN2 LS on SL RB set index and LBT failure indication for PSFCH |
MediaTek Inc. |
| R1-2310011 |
Draft reply LS on report quantity parameter setting for CQI reporting with 1Tx |
NTT DOCOMO, INC. |
| R1-2310012 |
Discussion on LS from RAN2 on Rel-18 AI/ML for air interface |
NTT DOCOMO, INC. |
| R1-2310092 |
Discussion on LS on SL RB set index and LBT failure indication for PSFCH |
Lenovo |
| R1-2310112 |
Discussion on the RAN1 impact to support for multicast reception in RRC_INACTIVE |
Qualcomm Incorporated |
| R1-2310113 |
Discussion on reply LS from RAN2 on XR capacity enhancements |
Qualcomm Incorporated |
| R1-2310114 |
Discussion for LS reply Part B to RAN2 on Data Collection Requirements and Assumptions |
Qualcomm Incorporated |
| R1-2310115 |
Reply to LS on SL positioning MAC agreements |
Qualcomm Incorporated |
| R1-2310116 |
Discussion for reply LS on power scaling and PHR in 38.213 |
Qualcomm Incorporated |
| R1-2310117 |
Discussion for reply LS on report quantity parameter setting for CQI reporting with 1Tx |
Qualcomm Incorporated |
| R1-2310118 |
Draft reply to the LS on the support of multiple location estimate instances in a single measurement report |
Qualcomm Incorporated |
| R1-2310191 |
Discussion on LS to RAN1 on the support of multiple location estimate instances in a single measurement report |
Ericsson |
| R1-2310192 |
[DRAFT] reply LS on the support of multiple location estimate instances in a single measurement report |
Ericsson |
| R1-2310193 |
Discussion on LS to RAN1 on SL positioning MAC agreements |
Ericsson |
| R1-2310194 |
[DRAFT] reply LS on SL positioning MAC agreements |
Ericsson |
| R1-2310208 |
Discussion on LS on Dual TCI state switching in mDCI |
Ericsson |
| R1-2310209 |
Discussion on reply LS on BAT and UE based TA measurement for LTM |
Ericsson |
| R1-2310210 |
Discussion on reply LS on PDCCH ordered RACH |
Ericsson |
| R1-2310216 |
[Draft] Reply LS on frequencyInfo for NR SL RSRP measurements |
Ericsson |
| R1-2310217 |
[Draft] Reply LS on SL RB set index and LBT failure indication for PSFCH |
Ericsson |
| R1-2310218 |
Discussion on SL RB set index and LBT failure indication for PSFCH |
Ericsson |
| R1-2310219 |
Discussion on RAN2 LS on RACH-less handover |
Ericsson |
| R1-2310239 |
Discussion on RAN4 LS on the system parameters for NTN above 10 GHz |
Ericsson |
| R1-2310246 |
Impact of MIMO power scaling on PHR in 38.213 |
Ericsson |
| R1-2310247 |
Draft reply LS on RAN1 impacts of enhancements to realize increasing UE power high limit for CA and DC |
Ericsson |
| R1-2310250 |
[Draft] Reply LS on power scaling and PHR in 38.213 |
Ericsson |
| R1-2310252 |
[Draft] reply to RAN2 LS on XR capacity enhancements |
Ericsson |
| R1-2310262 |
Discussion on RAN1 impact to support RAN4 work on NTN above 10GHz |
Huawei, HiSilicon |
| R1-2310264 |
Discussion on LS reply to RAN2 on data collection for AI/ML |
Huawei, HiSilicon |
| R1-2310269 |
Discussion on report quantity parameter setting for CQI reporting with 1Tx |
Huawei, HiSilicon |
| R1-2310270 |
Discussion on power scaling and PHR in 38.213 |
Huawei, HiSilicon |
| R1-2310271 |
Reply LS on monitoring of paging occasions for CG-SDT with HD-FDD RedCap UEs |
Huawei, HiSilicon |
| R1-2310274 |
Draft Reply LS on SL positioning MAC agreements |
Nokia, Nokia Shanghai Bell |
| R1-2310275 |
Discussion of RAN2 LS on SL positioning MAC agreements |
Nokia, Nokia Shanghai Bell |
| R1-2310503 |
Summary on multicast reception in RRC_INACTIVE |
Moderator (Apple) |
| R1-2310511 |
Draft reply LS on report quantity parameter setting for CQI reporting with 1Tx |
Moderator (ZTE) |
| R1-2310537 |
Summary on reply LS on report quantity parameter setting for CQI reporting with 1Tx |
Moderator (ZTE) |
| R1-2310557 |
Draft reply LS on Dual TCI state switching in mDCI |
Ericsson |
| R1-2310581 |
Reply LS on Dual TCI state switching in mDCI |
RAN1, Ericsson |
| R1-2310591 |
Summary of the discussion on LS on Dual TCI state switching in mDCI |
Moderator (Ericsson) |
| R1-2310597 |
Draft reply LS on multicast reception in RRC_INACTIVE |
Moderator (Apple) |
| R1-2310598 |
Reply LS on multicast reception in RRC_INACTIVE |
RAN1, Apple |
| R1-2310614 |
Summary#2 on reply LS on report quantity parameter setting for CQI reporting with 1Tx |
Moderator (ZTE) |
| R1-2310649 |
Reply LS on report quantity parameter setting for CQI reporting with 1Tx |
RAN1, ZTE |
| 6 |
Pre-Rel-18 E-UTRA Maintenance |
|
| R1-2309791 |
Draft CR on HARQ timing for CEMode B |
Lenovo |
| R1-2309887 |
Clarification on UL timing for CE Mode B |
Ericsson |
| R1-2310484 |
Draft CR on HARQ timing for CEMode B |
Moderator (Lenovo) |
| R1-2310485 |
Summary on HARQ timing for CEMode B |
Moderator (Lenovo) |
| R1-2310653 |
CR on HARQ timing for CEMode B |
Lenovo, Ericsson, Qualcomm Incorporated |
| R1-2310654 |
CR on HARQ timing for CEMode B |
Lenovo, Ericsson, Qualcomm Incorporated |
| R1-2310655 |
CR on HARQ timing for CEMode B |
Lenovo, Ericsson, Qualcomm Incorporated |
| R1-2310690 |
CR on HARQ timing for CEMode B |
Lenovo, Ericsson, Qualcomm Incorporated |
| R1-2310691 |
CR on HARQ timing for CEMode B |
Lenovo, Ericsson, Qualcomm Incorporated |
| 7.1 |
Maintenance on NR Releases 15 – 16 |
|
| R1-2308892 |
Correction on collision between NR PDSCH DMRS and LTE-CRS |
Huawei, HiSilicon |
| R1-2309027 |
Discussion on aperiodic triggering support for SRS carrier switching |
ZTE |
| R1-2309048 |
Draft Rel-16 CR on PUSCH selection rule for UCI multiplexing |
vivo |
| R1-2309215 |
Discussion on several ambiguities with type 2 CG-PUSCH DCI fields interpretation |
Ericsson |
| R1-2309349 |
Discussion on CSI-RS transmission occasion |
Samsung |
| R1-2309350 |
Correction on multiple DCIs per MO per CC for the Type-2 HARQ-ACK codebook |
Samsung |
| R1-2309351 |
Discussion on multiple DCIs per MO per CC for the Type-2 HARQ-ACK codebook |
Samsung |
| R1-2309352 |
On HARQ-ACK feedback enhancements for TDD-FDD CA |
Samsung, Verizon, CATT, Ericsson |
| R1-2309478 |
Clarification of HARQ-ACK for MsgB PDSCH |
CATT |
| R1-2309479 |
Clarification of HARQ-ACK for MsgB PDSCH |
CATT |
| R1-2309480 |
Correction on the HARQ-ACK mapping for CBG based transmission |
CATT |
| R1-2309481 |
Clarification on the first SPS PDSCH and Type2 CG PUSCH |
CATT |
| R1-2309482 |
Clarification on the first SPS PDSCH and Type2 CG PUSCH |
CATT |
| R1-2309571 |
Discussion on aperiodic triggering support for SRS carrier switching |
OPPO |
| R1-2309634 |
Discussion on aperiodic triggering of SRS carrier switching |
Fujitsu |
| R1-2309746 |
Clarifications relating to type 2 CG-PUSCH |
Huawei, HiSilicon |
| R1-2309747 |
Discussion on PUSCH selection rule for UCI multiplexing |
Huawei, HiSilicon |
| R1-2309751 |
Discussion on the HARQ-ACK Multiplexing in Multi-PUSCH scheduling |
Huawei, HiSilicon |
| R1-2309762 |
Draft CR correcting capability parameter for CSI trigger state non-active BWP |
Ericsson |
| R1-2309815 |
Discussion on PUSCH with repetitions or multi-PUSCHs with an UL DAI |
Apple |
| R1-2309816 |
Views on the 1st Type-2 CG PUSCH and ambiguities on activation DCI |
Apple |
| R1-2309817 |
On triggering A-SRS for carrier-based switching by a UE specific DCI |
Apple |
| R1-2309818 |
Discussion on ambiguity on initial state in Rel-16 UL Tx switching |
Apple |
| R1-2309819 |
Discussion on CR for NR PDSCH DMRS collision with LTE CRS and NR PDCCH |
Apple |
| R1-2309884 |
Discussion on several ambiguities with type 2 CG PUSCH |
ZTE |
| R1-2309895 |
On counting of active CSI-RS resources |
Nokia, Nokia Shanghai Bell |
| R1-2309896 |
Counting of active CSI-RS resources |
Nokia, Nokia Shanghai Bell |
| R1-2309897 |
On Path Loss reference RS for SCell UL PC when PL RS is not configured |
Nokia, Nokia Shanghai Bell |
| R1-2309898 |
Path Loss reference RS for SCell UL PC when PL RS is not configured |
Nokia, Nokia Shanghai Bell |
| R1-2309899 |
On SCell Type 1 virtual PHR reporting in UL CA |
Nokia, Nokia Shanghai Bell |
| R1-2309900 |
Clarification on SCell Type 1 virtual PHR reporting in UL CA |
Nokia, Nokia Shanghai Bell |
| R1-2309901 |
Clarification to multi-CSI-PUCCH-ResourceList |
Nokia, Nokia Shanghai Bell, Qualcomm Inc. |
| R1-2309959 |
Discussion on energy detection threshold formula for shared spectrum channel access |
Ericsson |
| R1-2309960 |
Draft CR on energy detection threshold formula for shared spectrum channel access |
Ericsson |
| R1-2309961 |
Discussion on clarification on SPS PDSCH |
Apple |
| R1-2309971 |
Clarify ambiguity on RRC reconfiguration with type 2 CG-PUSCH |
MediaTek Inc. |
| R1-2310013 |
Discussion of HARQ-ACK multiplexing on PUSCH repetition or multi-PUSCH |
NTT DOCOMO, INC. |
| R1-2310014 |
Draft CR on SL NACK report to gNB in mode 1 |
NTT DOCOMO, INC., vivo |
| R1-2310082 |
Discussion on UL DAI for multi-PUSCH scheduling |
Ericsson |
| R1-2310093 |
Discussion on the correction for multiple DL DCIs per MO per CC for Type 2 HARQ codebook |
Ericsson |
| R1-2310119 |
Clarify several ambiguities with type 2 CG-PUSCH |
Qualcomm Incorporated |
| R1-2310120 |
Clarify number of CDM groups without data for DMRS |
Qualcomm Incorporated |
| R1-2310121 |
Clarify CSI feedback with SUL |
Qualcomm Incorporated |
| R1-2310122 |
Issues on SRS carrier switching |
Qualcomm Incorporated |
| R1-2310123 |
Rel-16 Corrections to Applicable RRC States for Sidelink Measurements |
Qualcomm Incorporated |
| R1-2310126 |
Rel-17 Corrections to Applicable RRC States for Sidelink Measurements |
Qualcomm Incorporated |
| R1-2310203 |
Correction to the definition of RxTx measurements |
Ericsson |
| R1-2310204 |
On the definition of uplink and downlink subframes for positioning measurements |
Ericsson |
| R1-2310211 |
Draft CR on timing of a RACH procedure triggered by a PDCCH order |
Ericsson |
| R1-2310244 |
SRS Carrier Switching with DL DCI formats |
Ericsson, T-Mobile USA |
| R1-2310245 |
Correction for SRS carrier switching for DCI formats 1_1 and 1_2 |
Ericsson, T-Mobile USA |
| R1-2310253 |
Scheduling restriction for FDD-TDD UL CA |
Ericsson, Verizon |
| R1-2310254 |
Discussion on PUSCH selection rule for UCI multiplexing |
Ericsson |
| R1-2310263 |
Correction on the rate matching when HARQ-ACK multiplexed with CG-PUSCH |
Huawei, HiSilicon |
| R1-2310266 |
Discussion on scheduling reactivation for DL SPS |
Huawei, HiSilicon |
| R1-2310267 |
Draft CR on selection of CSI reports in a PUCCH |
Huawei, HiSilicon |
| R1-2310345 |
Scheduling restriction for FDD-TDD UL CA |
Ericsson, Verizon |
| R1-2310367 |
Discussion on selection of CSI reports in a PUCCH |
Huawei, HiSilicon |
| R1-2310418 |
CR correcting capability parameter for CSI trigger state non-active BWP |
Ericsson |
| R1-2310419 |
CR correcting capability parameter for CSI trigger state non-active BWP |
Ericsson |
| R1-2310420 |
CR correcting capability parameter for CSI trigger state non-active BWP |
Ericsson |
| R1-2310428 |
Summary of discussions on collision between NR PDSCH DMRS and LTE-CRS |
Moderator (Huawei) |
| R1-2310435 |
Summary of NR Rel-15/16 maintenance discussion for aperiodic triggering support for SRS carrier switching |
Moderator (Ericsson) |
| R1-2310436 |
Draft CR on selection of CSI reports in a PUCCH |
Huawei, HiSilicon |
| R1-2310437 |
Correction on the rate matching when HARQ-ACK multiplexed with CG-PUSCH |
Huawei, HiSilicon |
| R1-2310438 |
Correction on the rate matching when HARQ-ACK multiplexed with CG-PUSCH |
Huawei, HiSilicon |
| R1-2310439 |
Correction on the rate matching when HARQ-ACK multiplexed with CG-PUSCH |
Huawei, HiSilicon |
| R1-2310458 |
Summary of Discussion on RRC States for Sidelink Measurements |
Moderator (Qualcomm) |
| R1-2310468 |
Summary of discussion on CSI-RS transmission occasion |
Moderator (Samsung) |
| R1-2310473 |
Summary for discussion of HARQ-ACK multiplexing on PUSCH repetitions and multi-PUSCH scheduling |
Moderator (NTT DOCOMO, INC.) |
| R1-2310474 |
Draft CR on UL DAI for multi-PUSCH scheduling |
Moderator (NTT DOCOMO, INC.) |
| R1-2310479 |
[114bis-R15/16-NR] Summary of Counting of active CSI-RS resources |
Moderator (Nokia) |
| R1-2310480 |
[114bis-R15-16-NR] Summary on PL-RS for SCell UL PC |
Moderator (Nokia) |
| R1-2310481 |
[114bis-R15-16-NR] Summary of SCell Type 1 virtual PHR reporting |
Moderator (Nokia) |
| R1-2310482 |
[114bis-R15-16-NR] Summary on Clarification to multi-CSI-PUCCH-ResourceList |
Moderator (Nokia) |
| R1-2310495 |
Summary of discussion on scheduling issue for TDD-FDD UL CA |
Moderator (Samsung) |
| R1-2310507 |
FL summary #1 of clarifying several ambiguities with type 2 CG-PUSCH |
Moderator (Qualcomm) |
| R1-2310508 |
FL summary #1 of Clarify CSI feedback with SUL |
Moderator (Qualcomm) |
| R1-2310509 |
Summary of discussion on initial state ambiguity issue for UL Tx switching |
Moderator (Apple) |
| R1-2310512 |
Summary of discussion on the correction on Type-2 HARQ-ACK codebook for receiving multiple DCIs per MO per CC |
Moderator (Samsung) |
| R1-2310514 |
[Draft CR] Correction on multiple DCIs per MO per CC for the Type-2 HARQ-ACK codebook |
Moderator (Samsung) |
| R1-2310515 |
Discussion on reply LS on power scaling and PHR |
Moderator (vivo) |
| R1-2310516 |
Draft Reply LS on power scaling and PHR |
Moderator (vivo) |
| R1-2310517 |
Draft CR on energy detection threshold formula for shared spectrum channel access |
Ericsson, Samsung, Huawei |
| R1-2310520 |
Feature lead summary #1 on response LS for frequencyInfo for NR SL RSRP measurements |
Moderator (Huawei) |
| R1-2310521 |
Draft response LS for frequencyInfo for NR SL RSRP measurements |
Moderator (Huawei) |
| R1-2310522 |
Summary of discussion on PUSCH selection rule for UCI multiplexing |
Moderator (vivo) |
| R1-2310525 |
Summary of HARQ-ACK for MsgB PDSCH |
Moderator (CATT) |
| R1-2310526 |
Clarification of HARQ-ACK for MsgB PDSCH |
Moderator (CATT) |
| R1-2310527 |
Clarification of HARQ-ACK for MsgB PDSCH |
Moderator (CATT) |
| R1-2310528 |
Summary of clarification on the first SPS PDSCH and type2 CG PUSCH |
Moderator (CATT) |
| R1-2310529 |
Clarification on the first SPS PDSCH and Type2 CG PUSCH |
Moderator (CATT) |
| R1-2310530 |
Clarification on the first SPS PDSCH and Type2 CG PUSCH |
Moderator (CATT) |
| R1-2310551 |
Summary of discussion on scheduling reactivation for DL SPS |
Moderator (Huawei) |
| R1-2310552 |
Summary on selection of CSI reports in a PUCCH |
Moderator (Huawei) |
| R1-2310555 |
Reply LS on power scaling and PHR |
RAN1, vivo |
| R1-2310556 |
Summary of NR Rel-15/16 maintenance discussion for timing for PDCCH-ordered RACH |
Moderator (Ericsson) |
| R1-2310559 |
Response LS for frequencyInfo for NR SL RSRP measurements |
RAN1, Huawei |
| R1-2310560 |
CR on energy detection threshold formula for shared spectrum channel access for Rel-16 |
Ericsson, Samsung, Huawei |
| R1-2310561 |
CR on energy detection threshold formula for shared spectrum channel access for Rel-17 |
Ericsson, Samsung, Huawei |
| R1-2310562 |
CR on energy detection threshold formula for shared spectrum channel access for Rel-18 |
Ericsson, Samsung, Huawei |
| R1-2310563 |
Summary #1 for discussion on energy detection threshold formula for shared spectrum channel access |
Ericsson |
| R1-2310570 |
Miscellaneous corrections on TR 37.985 |
Huawei, HiSilicon |
| R1-2310571 |
Miscellaneous corrections on TR 37.985 |
Huawei, HiSilicon |
| R1-2310572 |
Revised summary of NR Rel-15/16 maintenance discussion for aperiodic triggering support for SRS carrier switching |
Moderator (Ericsson) |
| R1-2310573 |
FL summary on response LS for frequencyInfo for NR SL RSRP measurements |
Moderator (Huawei) |
| R1-2310586 |
Summary #2 of Discussion on RRC States for Sidelink Measurements |
Moderator (Qualcomm) |
| R1-2310588 |
Summary #2 for discussion of HARQ-ACK multiplexing on PUSCH repetitions and multi-PUSCH scheduling |
Moderator (NTT DOCOMO, INC.) |
| R1-2310589 |
Draft CR #2 on UL DAI for multi-PUSCH scheduling |
Moderator (NTT DOCOMO, INC.) |
| R1-2310646 |
FL summary #2 of clarifying several ambiguities with type 2 CG-PUSCH |
Moderator (Qualcomm) |
| R1-2310647 |
Summary#2 on selection of CSI reports in a PUCCH |
Moderator (Huawei) |
| R1-2310648 |
[Draft] Rel-16 Corrections to Applicable RRC States for Sidelink Measurements |
Moderator (Qualcomm) |
| R1-2310659 |
Corrections to Applicable RRC States for Sidelink Measurements |
Moderator (Qualcomm), Samsung, Huawei, HiSilicon, Nokia, NSB, vivo |
| R1-2310660 |
Corrections to Applicable RRC States for Sidelink Measurements |
Moderator (Qualcomm), Samsung, Huawei, HiSilicon, Nokia, NSB, vivo |
| R1-2310661 |
Corrections to Applicable RRC States for Sidelink Measurements |
Moderator (Qualcomm), Samsung, Huawei, HiSilicon, Nokia, NSB, vivo |
| R1-2310662 |
CR on SL NACK report to gNB in mode 1 (Rel-16) |
Moderator (NTT DOCOMO, INC.), vivo, Samsung, Qualcomm, Huawei, HiSilicon |
| R1-2310663 |
CR on SL NACK report to gNB in mode 1 (Rel-17) |
Moderator (NTT DOCOMO, INC.), vivo, Samsung, Qualcomm, Huawei, HiSilicon |
| R1-2310664 |
CR on SL NACK report to gNB in mode 1 (Rel-18) |
Moderator (NTT DOCOMO, INC.), vivo, Samsung, Qualcomm, Huawei, HiSilicon |
| R1-2310666 |
Correction on multiple DCIs per MO per CC for the Type-2 HARQ-ACK codebook |
Moderator (Samsung), Ericsson |
| R1-2310667 |
Correction on multiple DCIs per MO per CC for the Type-2 HARQ-ACK codebook |
Moderator (Samsung), Ericsson |
| R1-2310670 |
Correction on the rate matching when HARQ-ACK multiplexed with CG-PUSCH |
Huawei, HiSilicon, Samsung |
| R1-2310671 |
Correction on the rate matching when HARQ-ACK multiplexed with CG-PUSCH |
Huawei, HiSilicon, Samsung |
| R1-2310672 |
Correction on the rate matching when HARQ-ACK multiplexed with CG-PUSCH |
Huawei, HiSilicon, Samsung |
| R1-2310673 |
Path Loss reference RS for SCell UL PC when PL RS is not configured |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Samsung, Ericsson |
| R1-2310674 |
Path Loss reference RS for SCell UL PC when PL RS is not configured |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Samsung, Ericsson |
| R1-2310680 |
Summary#3 of NR Rel-15/16 maintenance discussion for aperiodic triggering support for SRS carrier switching |
Moderator (Ericsson) |
| R1-2310683 |
Clarification on the first SPS PDSCH and Type2 CG PUSCH |
Moderator (CATT) |
| R1-2310684 |
Clarification of HARQ-ACK for MsgB PDSCH |
Moderator (CATT), ZTE |
| R1-2310685 |
Clarification of HARQ-ACK for MsgB PDSCH |
Moderator (CATT), ZTE |
| 7.2 |
Maintenance on NR Release 17 |
|
| R1-2309028 |
Discussion on additional restrictions over CMR measurement for NCJT CSI |
ZTE |
| R1-2309029 |
Draft CR on additional restrictions over CMR measurement for NCJT CSI in TS 38.214 |
ZTE |
| R1-2309030 |
Draft CR on identifying unified TCI state from a reference CC in CA in TS 38.214 |
ZTE |
| R1-2309049 |
Draft Rel-17 CR on PUSCH selection rule for UCI multiplexing |
vivo |
| R1-2309050 |
Draft CR on referred PUCCH resources for multiplexing HARQ-ACK |
vivo |
| R1-2309051 |
Draft CR on intra-UE multiplexing for MBS |
vivo |
| R1-2309052 |
Discussion on remaining issues about overlapping among NACK-only, SR and other PUCCHs/PUSCHs |
vivo |
| R1-2309053 |
Draft CR on overlapping among NACK-only, SR and other PUCCHs/PUSCHs |
vivo |
| R1-2309054 |
Draft CR on UE procedure for reporting multiple UCI types including multicast HARQ-ACK |
vivo |
| R1-2309055 |
Draft CR on SSSG switching when monitoring multicast PDCCH in Type3 CSS |
vivo |
| R1-2309056 |
Discussion on DCI field interpretation for multi-PXSCH scheduling during BWP switching |
vivo |
| R1-2309057 |
Draft CR on DCI field interpretation for multi-PXSCH scheduling during BWP switching |
vivo |
| R1-2309058 |
Discussion on NCJT CSI reporting for DRX |
vivo |
| R1-2309059 |
Draft CR on NCJT CSI reporting for DRX |
vivo |
| R1-2309121 |
Draft CR on rate matching for PDSCH for MBS |
ZTE, CBN |
| R1-2309122 |
Draft CR on HARQ-ACK for one SPS PDSCH associated with G-CS-RNTI |
ZTE, CBN |
| R1-2309123 |
Draft CR on PDCCH monitoring for broadcast |
ZTE |
| R1-2309124 |
Draft CR on PDCCH skipping and SSSG switching for multicast in Type3 CSS |
ZTE |
| R1-2309125 |
Draft CR on PUCCH resource for multicast |
ZTE, CBN |
| R1-2309126 |
Draft CR on the total DAI |
ZTE |
| R1-2309127 |
Draft CR on Type0B-PDCCH CSS set |
ZTE, CBN |
| R1-2309128 |
Draft CR on Type1 codebook for maxCodeBlockGroupsPerTransportBlock |
ZTE, CBN |
| R1-2309129 |
Draft CR on intra-UE multiplexing for multicast |
ZTE, CBN |
| R1-2309130 |
Draft CR on Type-1 HARQ-ACK codebook for MBS |
ZTE, CBN |
| R1-2309131 |
Draft CR on HARQ-ACK reporting mode determination |
ZTE, CBN |
| R1-2309174 |
Correction on Rel-17 PDCCH monitoring adaptation |
ZTE, Sanechips |
| R1-2309175 |
Rel-17 RedCap maintenance issues |
ZTE, Sanechips |
| R1-2309176 |
Corrections on CD-SSB and NCD-SSB validation |
ZTE, Sanechips |
| R1-2309213 |
Discussion on scaling of angles for CDL models |
Ericsson |
| R1-2309214 |
Draft CR on scaling of angles for CDL models |
Ericsson |
| R1-2309267 |
Discussion on PUCCH transmission occasion |
Google |
| R1-2309268 |
draft CR on PUCCH transmission occasion |
Google |
| R1-2309269 |
Discussion on SRS transmission occasion |
Google |
| R1-2309270 |
draft CR on SRS transmission occasion |
Google |
| R1-2309299 |
Discussion on DCI field interpretation for multi-PxSCH scheduling and BWP switching |
LG Electronics |
| R1-2309300 |
Discussion on CSI related timeline for 480/960 kHz |
LG Electronics |
| R1-2309353 |
Draft CR on SRS for antenna switching |
Samsung |
| R1-2309354 |
Correction on the number of MBS SPS PDSCH repetitions |
Samsung |
| R1-2309355 |
Discussion on multiplexing Type-2 HARQ-ACK codebook in a PUSCH for multicast |
Samsung |
| R1-2309356 |
Correction on Type-2 HARQ-ACK codebook for multi-slot scheduling |
Samsung |
| R1-2309357 |
Correction on PUCCH power determination for Type-2 HARQ-ACK codebook |
Samsung |
| R1-2309358 |
Discussion on DCI interpretation for multi-PxSCH scheduling and BWP switching |
Samsung |
| R1-2309421 |
Discussion on remaining issues for SDT |
xiaomi |
| R1-2309422 |
Discussion on remaining issues for RedCap |
xiaomi |
| R1-2309423 |
Discussions on DCI interpretation for multi-PxSCH scheduling in BWP switching |
xiaomi |
| R1-2309483 |
Discussion on the remaining issues for multi-PXSCH scheduling during BWP switching in FR2-2 |
CATT |
| R1-2309484 |
Remaining issues of Rel-17 RedCap |
CATT |
| R1-2309485 |
Discussion on PUCCH power control parameter determination |
CATT |
| R1-2309486 |
Draft CR on PDCCH validation for multicast DL SPS |
CATT,CMCC,CBN |
| R1-2309487 |
Draft CR on PDCCH skipping/ SSSG switching for MBS multicast |
CATT, CBN |
| R1-2309488 |
Draft CR on the SCS and CP definition for multicast CFR and broadcast CFR |
CATT, CBN |
| R1-2309489 |
Draft CR on DL PRS priority determination with Priority indicator field in DCI format 4_2 |
CATT, CBN |
| R1-2309490 |
Draft CR on determination of multicast HARQ-ACK codebook reporting on PUSCH |
CATT, CBN |
| R1-2309491 |
Correction on the partial sensing occasion |
CATT, CICTCI |
| R1-2309545 |
Discussion on DCI based TCI state indication for unified TCI framework |
NEC |
| R1-2309546 |
Draft CR on positive HARQ-ACK for confirmation of DCI based TCI state indication in TS38.214 |
NEC |
| R1-2309547 |
Draft CR on no more than one indicated TCI state for unified TCI framework in TS38.214 |
NEC |
| R1-2309548 |
Draft CR on one from more than one indicated TCI state applied for unified TCI framework in TS38.214 |
NEC |
| R1-2309572 |
Discussion on CMR measurement restriction for NCJT CSI |
OPPO |
| R1-2309602 |
Type-1 HARQ-ACK codebook determination for Rel-17 NR-NTN |
OPPO |
| R1-2309603 |
Draft CR on Type-1 HARQ-ACK codebook determination for Rel-17 NR-NTN |
OPPO |
| R1-2309635 |
Clarification of CSI configuration for Rel-17 MTRP |
Fujitsu |
| R1-2309741 |
Introduction of LoS/NLoS abbreviations |
Huawei, HiSilicon |
| R1-2309749 |
Draft CR on PUCCH resources for multicast HARQ-ACK |
Huawei, HiSilicon, CBN |
| R1-2309750 |
Discussion on the maintenance issues for Rel-17 MBS |
Huawei, HiSilicon |
| R1-2309752 |
Discussion on the TDRA interpretation for multi-PDSCH/PUSCH scheduling during BWP switching in FR2-2 |
Huawei, HiSilicon |
| R1-2309754 |
Discussion on remaining issues for RedCap |
Huawei, HiSilicon |
| R1-2309757 |
Discussion on PDCCH monitoring during PDCCH skipping duration |
Huawei, HiSilicon |
| R1-2309758 |
Draft CR on PDCCH validation for multicast SPS |
Huawei, HiSilicon, CBN |
| R1-2309759 |
Draft CR on UE receiving both unicast and MBS broadcast |
Huawei, HiSilicon, CMCC, CBN |
| R1-2309760 |
Draft CR on monitoring PDCCH occasions for MBS broadcast |
Huawei, HiSilicon, CBN |
| R1-2309761 |
Draft CR on k1 timing for DCI format 4-1 |
Huawei, HiSilicon, CBN, CMCC |
| R1-2309885 |
Draft CR on the type 1 HARQ-ACK codebook in PUSCH |
ZTE, CBN |
| R1-2309892 |
Correction on minimum time gap for DCI format 2_6 |
ASUSTeK |
| R1-2309928 |
Draft CR on intra-UE multiplexing for multicast |
Nokia, Nokia Shanghai Bell |
| R1-2309989 |
K_offset for aperiodic SRS in Rel-17 NR NTN |
MediaTek Inc. |
| R1-2309990 |
Draft CR on K_offset for aperiodic SRS in Rel-17 NR NTN |
MediaTek Inc., ZTE |
| R1-2309991 |
K-offset for HARQ-ACK information for HARQ codebook in Rel-17 NR-NTN |
MediaTek Inc. |
| R1-2309992 |
Draft CR on K-offset for HARQ-ACK information for HARQ codebook in Rel-17 NR-NTN |
MediaTek Inc., Qualcomm |
| R1-2309999 |
Draft CR for correction on multicast SPS PDCCH validation |
MediaTek Inc. |
| R1-2310000 |
Draft CR for correction on PUCCH resource determination for NACK-only mode 1 with one bit HARQ-ACK |
MediaTek Inc. |
| R1-2310015 |
Discussion on NCJT CMR restriction |
NTT DOCOMO, INC. |
| R1-2310016 |
Discussion on the issues for multi-PXSCH scheduling during DCI-based BWP switching |
NTT DOCOMO, INC. |
| R1-2310017 |
Draft CR on the interpretation of the number of scheduled PXSCH during DCI-based BWP switching |
NTT DOCOMO, INC. |
| R1-2310018 |
Draft CR on NDI/RV for the scheduled PXSCHs when BWP switching is indicated |
NTT DOCOMO, INC. |
| R1-2310019 |
Discussion on remaining issues for RedCap UE |
NTT DOCOMO, INC. |
| R1-2310020 |
Draft CR on paging occasions and CG-SDT for HD-FDD RedCap |
NTT DOCOMO, INC. |
| R1-2310021 |
Draft CR on determination of processing time for MBS PDSCH without feedback |
NTT DOCOMO, INC. |
| R1-2310083 |
Discussion on A-CSI-RS triggering offset for FR2_2 |
Ericsson |
| R1-2310084 |
Discussion on DCI field interpretation for multi-PXSCH scheduling during BWP switching |
Ericsson |
| R1-2310086 |
Draft CR on the determining of DCI size for multi-PxSCH scheduling during BWP switching |
ZTE, Sanechips |
| R1-2310087 |
Draft CR on the determining of DCI size for multi-PUSCH scheduling during BWP switching |
ZTE, Sanechips |
| R1-2310088 |
Discussion on the determining of DCI size for multi-PxSCH scheduling during BWP switching |
ZTE, Sanechips |
| R1-2310101 |
Correction on RRC parameter name for SDT in TS38.214 |
Sharp |
| R1-2310124 |
Draft CR on SSSG switching when monitoring multicast PDCCH in Type3 CSS |
Qualcomm Incorporated |
| R1-2310125 |
Discussion of remaining Issues for Procedures of RedCap UE |
Qualcomm Incorporated |
| R1-2310186 |
Draft CR on the interpretation of the number of scheduled PXSCH during DCI-based BWP switching |
NTT DOCOMO, INC. |
| R1-2310187 |
Draft CR on NDI/RV for the scheduled PXSCHs when BWP switching is indicated |
NTT DOCOMO, INC. |
| R1-2310205 |
Correction to the definition of TA measurements |
Ericsson |
| R1-2310224 |
Monitoring of paging occasions for CG-SDT with HD-FDD RedCap UEs |
Ericsson |
| R1-2310251 |
Correction on CBR related parameters names in TS 38.215 |
Intel Corporation |
| R1-2310258 |
Discussion on SRS spatial relation |
Huawei, HiSilicon |
| R1-2310259 |
Discussion on the starting symbol of subslot based PUCCH repetition in 38.213 |
Huawei, HiSilicon |
| R1-2310260 |
Correction on the starting symbol of subslot based PUCCH repetition in 38.213 |
Huawei, HiSilicon |
| R1-2310265 |
Draft CR on Type1A search space |
Huawei, HiSilicon |
| R1-2310268 |
Correction on Rel-17 per-TRP beam failure recovery |
Huawei, HiSilicon |
| R1-2310272 |
Discussion on NCJT CMR restriction |
Huawei, HiSilicon |
| R1-2310273 |
Draft CR on NCJT CMR restriction |
Huawei, HiSilicon |
| R1-2310276 |
Correction to PDCCH skipping procedure when a UE reports NACK |
Samsung |
| R1-2310277 |
Correction to PDCCH skipping procedure when a UE reports NACK |
Samsung |
| R1-2310306 |
FL Summary #1 for maintenance on R17 positioning |
Moderator (CATT) |
| R1-2310322 |
FL summary #1 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2310323 |
FL summary #2 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2310324 |
FL summary #3 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2310325 |
RAN1 agreements for Rel-17 NR RedCap |
Rapporteur (Ericsson) |
| R1-2310339 |
Discussion on angle scaling procedure for CDL channel in TR38.901 |
Intel Corporation |
| R1-2310340 |
Draft Correction of angle scaling procedure for CDL channel in TR38.901 |
Intel Corporation |
| R1-2310341 |
Summary #1 of FR2-2 maintenance |
Moderator (LG Electronics) |
| R1-2310346 |
Moderator Summary for Rel.17 NR FeMIMO maintenance CSI enhancement |
Moderator (Huawei) |
| R1-2310347 |
Moderator’s summary#1 on scheduling related issues for Rel-17 NR MBS |
Moderator (CMCC) |
| R1-2310348 |
Moderator’s summary#2 on scheduling related issues for Rel-17 NR MBS |
Moderator (CMCC) |
| R1-2310349 |
Moderator Summary#1 of Maintenance on Rel-17 SRS |
Moderator (ZTE) |
| R1-2310359 |
Moderator Summary for Rel.17 NR FeMIMO maintenance: mTRP beam management |
Moderator (CATT) |
| R1-2310375 |
Moderator Summary #1 for Maintenance on Rel-17 Multi-Beam |
Moderator (ZTE) |
| R1-2310376 |
Summary for Rel.17 NR FeMIMO maintenance: mTRP PUCCH |
Moderator (Nokia) |
| R1-2310379 |
Moderator summary#1 of Rel-17 URLLC & IIoT maintenance |
Moderator (Nokia) |
| R1-2310397 |
FL Summary #1: Rel-17 NR NTN maintenance |
Moderator (Thales) |
| R1-2310398 |
Moderator Summary #1 for AI 7.2: Maintenance on NR Sidelink enhancement |
Moderator (LG Electronics) |
| R1-2310399 |
Moderator Summary #2 for AI 7.2: Maintenance on NR Sidelink enhancement |
Moderator (LG Electronics) |
| R1-2310404 |
FLS#1 on the HARQ-ACK related issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2310405 |
FLS#2 on the HARQ-ACK related issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2310406 |
FLS#3 on the HARQ-ACK related issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2310407 |
Draft CR on Type-1 HARQ-ACK codebook |
Moderator (Huawei), ZTE |
| R1-2310408 |
Draft CR on PUCCH resources for multicast HARQ-ACK |
Moderator (Huawei) |
| R1-2310409 |
Draft CR on Type-1 HARQ-ACK on PUSCH |
Moderator (Huawei), ZTE |
| R1-2310410 |
Draft CR on the total DAI for Type-2 HARQ-ACK codebook |
Moderator (Huawei), ZTE |
| R1-2310411 |
Summary#1 for maintenance on UE power saving enhancements |
Moderator (MediaTek) |
| R1-2310415 |
Summary#1 on Rel-17 SDT |
Moderator (ZTE) |
| R1-2310421 |
Summary for reply LS on multiple location estimate instances in single measurement |
Moderator (ZTE) |
| R1-2310422 |
Draft reply LS on support of multiple location estimate instances in a single measurement |
Moderator (ZTE) |
| R1-2310423 |
Draft CR on HARQ codebook for maxCodeBlockGroups |
Moderator (Huawei) |
| R1-2310440 |
Moderator Summary for Rel.17 NR FeMIMO maintenance: mTRP beam management (Round 2) |
Moderator (CATT) |
| R1-2310446 |
Summary #2 of FR2-2 maintenance |
Moderator (LG Electronics) |
| R1-2310447 |
Correction on minimum time gap for DCI format 2_6 |
Moderator (LG Electronics), ASUSTeK, Samsung |
| R1-2310448 |
Correction on minimum time gap for DCI format 2_6 |
Moderator (LG Electronics), ASUSTeK, Samsung |
| R1-2310459 |
Draft CR on HARQ codebook for maxCodeBlockGroups |
Moderator (Huawei) |
| R1-2310460 |
Draft CR on Type-2 HARQ-ACK codebook on PUSCH |
Moderator (Huawei), CATT |
| R1-2310461 |
Draft CR on Type-1 HARQ-ACK codebook |
Moderator (Huawei), ZTE |
| R1-2310462 |
Draft CR on intra-UE HARQ-ACK multiplexing |
Moderator (Huawei) |
| R1-2310463 |
Draft CR on Type-1 HARQ-ACK on PUSCH |
Moderator (Huawei), ZTE |
| R1-2310464 |
Draft CR on HARQ-ACK for SPS PDSCH |
Moderator (Huawei), ZTE |
| R1-2310465 |
Moderator Summary #2 for Maintenance on Rel-17 Multi-Beam |
Moderator (ZTE) |
| R1-2310467 |
Moderator Summary#2 of Maintenance on Rel-17 SRS |
Moderator (ZTE) |
| R1-2310469 |
Correction on Type1A search space for SDT |
Moderator(ZTE), Huawei, HiSilicon, Ericsson, Samsung, New H3C |
| R1-2310470 |
Correction on Type1A search space for SDT |
Moderator(ZTE), Huawei, HiSilicon, Ericsson, Samsung, New H3C |
| R1-2310472 |
Moderator summary#2 of Rel-17 URLLC & IIoT maintenance |
Moderator (Nokia) |
| R1-2310493 |
Moderator Summary for Rel.17 NR FeMIMO maintenance – Round 2: CSI Enhancement |
Moderator (Huawei) |
| R1-2310510 |
Moderator Summary #2 for Maintenance on Rel-17 Multi-Beam |
Moderator (ZTE) |
| R1-2310524 |
Draft CR on downlink DAI |
Moderator (Huawei), ZTE |
| R1-2310531 |
Corrections on Partial Sensing Occasion |
Moderator (LG Electronics), CATT, CICTCI, Samsung, ZTE, Sanechips, Nokia, Nokia Shanghai Bell |
| R1-2310532 |
Corrections on Partial Sensing Occasion |
Moderator (LG Electronics), CATT, CICTCI, Samsung, ZTE, Sanechips, Nokia, Nokia Shanghai Bell |
| R1-2310533 |
Moderator Summary #3 for AI 7.2: Maintenance on NR Sidelink enhancement |
Moderator (LG Electronics) |
| R1-2310538 |
Session notes for 7.2 (Maintenance on supporting NR from 52.6GHz to 71 GHz) |
Ad-Hoc Chair (Huawei) |
| R1-2310539 |
Session notes for 7.2 (Maintenance on NR Multicast and Broadcast Services) |
Ad-Hoc Chair (Huawei) |
| R1-2310550 |
Summary#2 for maintenance on UE power saving enhancements |
Moderator (MediaTek) |
| R1-2310565 |
Draft LS on NCD-SSB time offset for RedCap UEs in TDD |
Ericsson |
| R1-2310566 |
LS on NCD-SSB time offset for RedCap UEs in TDD |
RAN1, Ericsson |
| R1-2310585 |
Moderator Summary #4 for AI 7.2: Maintenance on NR Sidelink enhancement |
Moderator (LG Electronics) |
| R1-2310590 |
Summary#2 on Rel-17 SDT |
Moderator (ZTE) |
| R1-2310602 |
Correction on Type-2 HARQ-ACK codebook for multi-slot scheduling |
Moderator (LG Electronics), Samsung |
| R1-2310603 |
Correction on Type-2 HARQ-ACK codebook for multi-slot scheduling |
Moderator (LG Electronics), Samsung |
| R1-2310604 |
Correction on PUCCH power determination for Type-2 HARQ-ACK codebook |
Moderator (LG Electronics), Samsung |
| R1-2310605 |
Correction on PUCCH power determination for Type-2 HARQ-ACK codebook |
Moderator (LG Electronics), Samsung |
| R1-2310606 |
Correction on Type-2 HARQ-ACK codebook for multi-slot scheduling |
Moderator (LG Electronics), Samsung, Ericsson |
| R1-2310607 |
Correction on Type-2 HARQ-ACK codebook for multi-slot scheduling |
Moderator (LG Electronics), Samsung, Ericsson |
| R1-2310608 |
Correction on PUCCH power determination for Type-2 HARQ-ACK codebook |
Moderator (LG Electronics), Samsung |
| R1-2310609 |
Correction on PUCCH power determination for Type-2 HARQ-ACK codebook |
Moderator (LG Electronics), Samsung |
| R1-2310610 |
CR on Type-2 HARQ-ACK codebook on PUSCH |
Moderator (Huawei), CATT, CBN |
| R1-2310611 |
CR on Type-2 HARQ-ACK codebook on PUSCH |
Moderator (Huawei), CATT, CBN |
| R1-2310612 |
CR on PUCCH resources for multicast HARQ-ACK |
Moderator (Huawei), vivo, ZTE |
| R1-2310613 |
CR on PUCCH resources for multicast HARQ-ACK |
Moderator (Huawei), vivo, ZTE |
| R1-2310639 |
Correction on SL RSSI measurement threshold related parameter name |
Moderator (LG Electronics), Intel Corporation, Samsung |
| R1-2310640 |
Correction on SL RSSI measurement threshold related parameter name |
Moderator (LG Electronics), Intel Corporation, Samsung |
| R1-2310641 |
Correction on SL RSSI measurement threshold related parameter name |
Moderator (LG Electronics), Intel Corporation, Samsung |
| R1-2310665 |
Moderator Summary for Rel.17 NR FeMIMO maintenance – Round 2: CSI Enhancement |
Moderator (Huawei) |
| R1-2310668 |
CR on one from more than one indicated TCI state applied for unified TCI framework in TS38.214 |
Moderator (ZTE), NEC, Samsung, NTT DOCOMO |
| R1-2310669 |
CR on one from more than one indicated TCI state applied for unified TCI framework in TS38.214 |
Moderator (ZTE), NEC, Samsung, NTT DOCOMO |
| R1-2310675 |
Reply LS on support of multiple location estimate instances in a single measurement |
RAN1, ZTE |
| R1-2310724 |
Rel-17 editorial corrections for TS 38.212 |
Huawei |
| R1-2310725 |
Rel-17 editorial corrections for TS 38.213 |
Samsung |
| R1-2310726 |
Rel-17 editorial corrections for TS 38.214 |
Nokia |
| R1-2310727 |
Rel-17 editorial corrections for TS 38.212 (mirrored to Rel-18) |
Huawei |
| R1-2310728 |
Rel-17 editorial corrections for TS 38.213 (mirrored to Rel-18) |
Samsung |
| R1-2310729 |
Rel-17 editorial corrections for TS 38.214 (mirrored to Rel-18) |
Nokia |
| 8 |
Rel-18 |
|
| R1-2310692 |
Consolidated Rel-18 higher layers parameter list |
Moderator (Ericsson) |
| R1-2310693 |
DRAFT LS on Rel-18 higher-layers parameter list |
Moderator (Ericsson) |
| R1-2310694 |
LS on Rel-18 higher-layers parameter list |
RAN1, Ericsson |
| R1-2310695 |
Collection of updated Rel-18 higher layers parameter list |
Moderator (Ericsson) |
| R1-2310696 |
Email discussion summary on LS for Rel-18 higher layer parameters |
Moderator (Ericsson) |
| R1-2310697 |
Summary of email discussions [Post-114bis-38.213-NR_mob_enh2] |
Moderator (Samsung) |
| R1-2310698 |
Summary of email discussions [Post-114bis-38.213-NR_MC_Enh] |
Moderator (Samsung) |
| R1-2310699 |
Summary of email discussions [Post-114bis-38.213-NR_MIMO_evo_DL_UL] |
Moderator (Samsung) |
| R1-2310700 |
Summary of email discussions [Post-114bis-38.213-NR_NCR] |
Moderator (Samsung) |
| R1-2310701 |
Summary of email discussions [Post-114bis-38.213-NR_Netw_Energy_NR] |
Moderator (Samsung) |
| R1-2310702 |
Summary of email discussions [Post-114bis-38.213-NR_pos_enh2] |
Moderator (Samsung) |
| R1-2310703 |
Summary of email discussions [Post-114bis-38.213-NR_SL_enh2] |
Moderator (Samsung) |
| R1-2310704 |
Discussion summary for TS38.215 draft CR for Rel-18 NR NTN enhancements |
Moderator (Intel Corporation) |
| R1-2310705 |
Discussion summary for TS38.215 draft CR for Rel-18 positioning enhancements |
Moderator (Intel Corporation) |
| R1-2310706 |
Summary of email discussion [Post-114bis-38.212-NR_pos_enh2-Core] |
Moderator (Huawei) |
| R1-2310707 |
Summary of email discussion [Post-114bis-38.212-NR_SL_enh2-Core] |
Moderator (Huawei) |
| R1-2310708 |
Summary of email discussion [Post-114bis-38.212-NR_MIMO_evo_DL_UL] |
Moderator (Huawei) |
| R1-2310709 |
Summary of email discussion [Post-114bis-38.212-NR_MC_enh] |
Moderator (Huawei) |
| R1-2310710 |
Summary of email discussion [Post-114bis-38.212-Netw_Energy_NR-Core] |
Moderator (Huawei) |
| R1-2310711 |
Editor’s summary on draft CR 37.213 for SL-U |
Moderator (Ericsson) |
| R1-2310712 |
Editor’s summary on draft CR 38.211 for NR_LessThan_5MHz_FR1-Core |
Moderator (Ericsson) |
| R1-2310713 |
Editor’s summary on draft CR 38.211 for NR_MIMO_evo_DL_UL-Core |
Moderator (Ericsson) |
| R1-2310714 |
Editor’s summary on draft CR 38.211 for NR_pos_enh2-Core |
Moderator (Ericsson) |
| R1-2310715 |
Summary on email discussion on Netw_Energy_NR |
Moderator (Nokia) |
| R1-2310716 |
Summary of email discussion on NR_MIMO enhancements on CSI |
Moderator (Nokia) |
| R1-2310717 |
Summary of email discussion on NR_MIMO enhancements on uTCI_STxMP_DMRS_SRS_8Tx_2TA |
Moderator (Nokia) |
| R1-2310718 |
Summary on email discussion on NR_Mob_enh2 |
Moderator (Nokia) |
| R1-2310719 |
Summary on email discussion on NR_NTN_enh-Core |
Moderator (Nokia) |
| R1-2310720 |
Summary on email discussion on NR Enhanced Positioning |
Moderator (Nokia) |
| R1-2310721 |
Summary on email discussion on Sidelink enhancements |
Moderator (Nokia) |
| R1-2310722 |
Summary on email discussion on Red Cap enhancements |
Moderator (Nokia) |
| R1-2310723 |
Summary of email discussion on the introduction of UL Tx switching across up to 4 bands in [Post-114bis-38.214-MC_Enh] |
Moderator (Nokia) |
| R1-2310730 |
Maintenance of further NR coverage enhancements |
Samsung |
| R1-2310731 |
Maintenance of further mobility enhancements |
Samsung |
| R1-2310732 |
Maintenance of dynamic spectrum sharing (DSS) enhancements |
Samsung |
| R1-2310733 |
Maintenance of multi-carrier enhancements for NR |
Samsung |
| R1-2310734 |
Maintenance of MIMO Evolution for Downlink and Uplink |
Samsung |
| R1-2310735 |
Maintenance of Network Controlled Repeaters |
Samsung |
| R1-2310736 |
Maintenance of network energy savings for NR |
Samsung |
| R1-2310737 |
Maintenance of expanded and improved NR positioning |
Samsung |
| R1-2310738 |
Maintenance of support for enhanced reduced capability NR devices |
Samsung |
| R1-2310739 |
Maintenance of NR sidelink evolution |
Samsung |
| R1-2310740 |
Maintenance of XR enhancements for NR |
Samsung |
| R1-2310741 |
Correction of Rel-19 MIMO evolution |
Intel Corporation |
| R1-2310742 |
Correction of Rel-18 NR NTN enhancements |
Intel Corporation |
| R1-2310743 |
Correction of Rel-18 Positioning Enhancements |
Intel Corporation |
| R1-2310744 |
Corrections on NR positioning enhancement in 38.212 |
Huawei |
| R1-2310745 |
Corrections on Rel-18 NR sidelink evolution in 38.212 |
Huawei |
| R1-2310746 |
Corrections on Rel-18 further NR Coverage enhancement in 38.212 |
Huawei |
| R1-2310747 |
Corrections on Rel-18 Further NR mobility enhancements in 38.212 |
Huawei |
| R1-2310748 |
Corrections on Rel-18 MIMO Evolution for Downlink and Uplink in 38.212 |
Huawei |
| R1-2310749 |
Corrections on Rel-18 Multi-carrier enhancements in 38.212 |
Huawei |
| R1-2310750 |
Corrections on Rel-18 network energy saving for NR in 38.212 |
Huawei |
| R1-2310751 |
Corrections on Rel-18 NR NTN enhancements in 38.212 |
Huawei |
| R1-2310752 |
Corrections on Rel-18 XR enhancements for NR in 38.212 |
Huawei |
| R1-2310753 |
Maintenance of NR Sidelink operation on shared spectrum |
Ericsson |
| R1-2310754 |
Corrections to NR Dynamic Spectrum Sharing (DSS) |
Ericsson |
| R1-2310755 |
Corrections to NR support for dedicated spectrum less than 5MHz for FR1 |
Ericsson |
| R1-2310756 |
Corrections to MIMO enhancements |
Ericsson |
| R1-2310757 |
Corrections to NR Network-controlled Repeaters |
Ericsson |
| R1-2310758 |
Corrections to positioning enhancements |
Ericsson |
| R1-2310759 |
Correction of specification support for network energy saving |
Nokia |
| R1-2310760 |
Correction of specification support for MIMO enhancements on CSI |
Nokia |
| R1-2310761 |
Correction of specification support for MIMO enhancements on uTCI_STxMP_DMRS_SRS_8Tx_2TA |
Nokia |
| R1-2310762 |
Corrections of specification support for mobility enhancements |
Nokia |
| R1-2310763 |
Correction of specification support for NR NTN enhancements |
Nokia |
| R1-2310764 |
Corrections on the support for Expanded and Improved NR Positioning |
Nokia |
| R1-2310765 |
Correction of enhancements for NR sidelink evolution |
Nokia |
| R1-2310766 |
Corrections on further NR coverage enhancements |
Nokia |
| R1-2310767 |
Correction of enhanced reduced capability NR devices |
Nokia |
| R1-2310768 |
Corrections of XR Enhancements for NR |
Nokia |
| R1-2310769 |
Introduction of UL Tx switching across up to 4 bands |
Nokia |
| R1-2310770 |
Summary of email discussions [Post-114bis-36.213-IoT_NTN_enh-Core] |
Moderator (Motorola Mobility) |
| R1-2310771 |
Corrections to IoT (Internet of Things) NTN (non-terrestrial network) enhancements |
Motorola Mobility |
| R1-2310772 |
Corrections on further NR coverage enhancements |
Nokia |
| 8.1 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
|
| R1-2309359 |
RRC parameters for Rel-18 NR MIMO |
Moderator (Samsung) |
| 8.1.1.1 |
Unified TCI framework extension for multi-TRP |
|
| R1-2308923 |
Maintenance of unified TCI framework extension for multi-TRP |
Huawei, HiSilicon |
| R1-2308931 |
Unified TCI framework extension for multi-TRP |
FUTUREWEI |
| R1-2308951 |
Discussions on the remaining issue on Unified TCI framework extension for multi-TRP |
New H3C Technologies Co., Ltd. |
| R1-2308959 |
Remaining Details on Rel-18 Unified TCI for MTRP |
InterDigital, Inc. |
| R1-2308973 |
Remaining issues on unified TCI framework extension for multi-TRP |
Spreadtrum Communications |
| R1-2309013 |
Maintenance on unified TCI framework extension for multi-TRP |
ZTE |
| R1-2309060 |
Maintenance on unified TCI framework extension for multi-TRP |
vivo |
| R1-2309159 |
Maintenance of unified TCI framework extension for multi-TRP |
Ericsson |
| R1-2309163 |
Unified TCI framework extension for multi-TRP/panel |
LG Electronics |
| R1-2309208 |
Unified TCI Framework Extension for Multi-TRP |
Intel Coporation |
| R1-2309231 |
Discussion on unified TCI framework extension for multi-TRP |
Hyundai Motor Company |
| R1-2309282 |
Remaining issues on unified TCI framework extension for multi-TRP |
NEC |
| R1-2309315 |
Maintenance on unified TCI framework for multi-TRP |
Lenovo |
| R1-2309360 |
Views on unified TCI extension focusing on m-TRP |
Samsung |
| R1-2309424 |
Remaining issues on unified TCI framework extension for multi-TRP |
xiaomi |
| R1-2309493 |
Remaining issues on unified TCI framework extension for multi-TRP |
CATT |
| R1-2309563 |
Remaining issue of unified TCI framework extension for multi-TRP |
OPPO |
| R1-2309636 |
Discussion on unified TCI framework extension for multi-TRP |
Fujitsu |
| R1-2309659 |
Remaining issues on unified TCI framework extension for multi-TRP |
CMCC |
| R1-2309714 |
Remaining issues of unified TCI framework extension for multi-TRP |
Transsion Holdings |
| R1-2309763 |
Discussions on unified TCI framework extension for multi-TRP |
Ruijie Network Co. Ltd |
| R1-2309784 |
Discussion on unified TCI framework extension for multi-TRP |
Google |
| R1-2309802 |
Discussion on unified TCI framework extension for multi-TRP operation |
TCL |
| R1-2309820 |
Unified TCI framework extension for multi-TRP |
Apple |
| R1-2309915 |
Maintenance of unified TCI framework extension for multi-TRP |
Nokia, Nokia Shanghai Bell |
| R1-2309933 |
Remaining issues on unified TCI framework extension for multi-TRP |
Panasonic |
| R1-2309962 |
Maintenance on unified TCI framework extension for multi-TRP |
Sharp |
| R1-2309978 |
Remaining issues on unified TCI framework extension for multi-TRP |
MediaTek Inc. |
| R1-2310022 |
Remaining issues on unified TCI framework extension for multi-TRP |
NTT DOCOMO, INC. |
| R1-2310127 |
Extension of unified TCI framework for mTRP |
Qualcomm Incorporated |
| R1-2310206 |
Moderator summary on extension of unified TCI framework (Round 0) |
Moderator (MediaTek Inc.) |
| R1-2310207 |
Moderator summary on extension of unified TCI framework (Round 1) |
Moderator (MediaTek Inc.) |
| R1-2310229 |
Multi-TRP enhancements for the unified TCI framework |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2310455 |
Moderator summary on extension of unified TCI framework (Round 2) |
Moderator (MediaTek Inc.) |
| R1-2310504 |
Summary of agreed TP for Rel-18 Unified TCI framework extension |
Moderator (MediaTek Inc.) |
| R1-2310505 |
Moderator summary on extension of unified TCI framework (Round 3) |
Moderator (MediaTek Inc.) |
| R1-2310658 |
Moderator summary on extension of unified TCI framework (Final) |
Moderator (MediaTek Inc.) |
| 8.1.1.2 |
Two TAs for multi-DCI |
|
| R1-2308924 |
Maintenance of TA enhancement for UL M-TRP transmission |
Huawei, HiSilicon |
| R1-2308932 |
Enhancements to support two TAs for multi-DCI |
FUTUREWEI |
| R1-2308960 |
Remaining Details on Rel-18 Multiple TA Operation |
InterDigital, Inc. |
| R1-2308974 |
Remaining issues on two TAs for multi-DCI based multi-TRP |
Spreadtrum Communications |
| R1-2309014 |
Maintenance on TA enhancement for multi-DCI |
ZTE |
| R1-2309061 |
Maintenance on two TAs for multi-DCI-based multi-TRP operation |
vivo |
| R1-2309160 |
Maintenance of two TAs for multi-DCI |
Ericsson |
| R1-2309164 |
Two TAs for multi-TRP/panel |
LG Electronics |
| R1-2309202 |
On two TAs for multi-DCI |
Intel Coporation |
| R1-2309283 |
Remaining issues on two TAs for multi-DCI |
NEC |
| R1-2309316 |
Remaining issue of two TAs for multi-DCI UL transmission |
Lenovo |
| R1-2309361 |
Remaining details on two TAs for m-DCI |
Samsung |
| R1-2309425 |
Discussion on two TAs for multi-TRP operation |
xiaomi |
| R1-2309494 |
Remaining issues on two TAs for UL multi-DCI multi-TRP operation |
CATT |
| R1-2309564 |
Remaining issue of two TAs for multi-DCI based multi-TRP operation |
OPPO |
| R1-2309660 |
Remaining issues on two TAs for multi-DCI |
CMCC |
| R1-2309715 |
Remaining issues of two TAs for multi-DCI based multi-TRP operation |
Transsion Holdings |
| R1-2309764 |
Discussions on two TAs for multi-DCI |
Ruijie Network Co. Ltd |
| R1-2309785 |
Discussion on two TAs for multi-DCI |
Google |
| R1-2309790 |
Discussion on multi-TA Cells for beam failure recovery |
ASUSTEK |
| R1-2309821 |
Two TAs for multi-DCI mTRP |
Apple |
| R1-2309916 |
Maintenance of two TAs for UL multi-DCI multi-TRP operation |
Nokia, Nokia Shanghai Bell |
| R1-2309963 |
Maintenance on two TAs for multi-DCI |
Sharp |
| R1-2310023 |
Remaining issues on two TAs for multi-DCI |
NTT DOCOMO, INC. |
| R1-2310128 |
Supporting two TAs for multi-DCI based mTRP |
Qualcomm Incorporated |
| R1-2310357 |
Moderator Summary #1 on Two TAs for multi-DCI |
Moderator (Ericsson) |
| R1-2310432 |
Moderator Summary #2 on Two TAs for multi-DCI |
Moderator (Ericsson) |
| R1-2310554 |
Moderator Summary #3 on Two TAs for multi-DCI |
Moderator (Ericsson) |
| 8.1.2 |
CSI enhancement |
|
| R1-2308925 |
Maintenance of` CSI enhancement for coherent JT and mobility |
Huawei, HiSilicon |
| R1-2308961 |
Remaining Details on Rel-18 CSI Enhancements |
InterDigital, Inc. |
| R1-2308975 |
Remaining issues on CSI enhancement |
Spreadtrum Communications |
| R1-2309015 |
Maintenance on CSI enhancement for high/medium UE velocities and CJT |
ZTE |
| R1-2309062 |
Maintenance on CSI enhancement |
vivo |
| R1-2309206 |
On CSI enhancements for NR |
Intel Coporation |
| R1-2309254 |
On CSI Enhancement |
Google |
| R1-2309274 |
Remaining issues on CSI enhancement |
NEC |
| R1-2309317 |
Discussion of CSI enhancement for high speed UE and coherent JT |
Lenovo |
| R1-2309362 |
Moderator summary on Rel-18 CSI enhancements |
Moderator (Samsung) |
| R1-2309363 |
Views on CSI enhancements |
Samsung |
| R1-2309426 |
Maintenance on CSI enhancement for high/medium UE velocities and CJT |
xiaomi |
| R1-2309495 |
Maintenance on CSI enhancement |
CATT |
| R1-2309565 |
Remaining issues on CSI enhancement for high/medium UE velocities and coherent JT |
OPPO |
| R1-2309637 |
Maintenance on Rel-18 CSI enhancements |
Fujitsu |
| R1-2309661 |
Remaining issues on CSI enhancement for high/medium UE velocities and CJT |
CMCC |
| R1-2309765 |
Discussions on CSI enhancement |
Ruijie Network Co. Ltd |
| R1-2309822 |
Views on Rel-18 MIMO CSI enhancement |
Apple |
| R1-2309917 |
Maintenance of CSI enhancement for high/medium UE velocities and CJT |
Nokia, Nokia Shanghai Bell |
| R1-2310024 |
Remaining issues on CSI enhancement |
NTT DOCOMO, INC. |
| R1-2310085 |
Remaining issues on CSI for Rel-18 NR MIMO evolution |
Ericsson |
| R1-2310129 |
Remaining issues and maintenance on Rel-18 CSI enhancement |
Qualcomm Incorporated |
| R1-2310228 |
CSI enhancements for medium UE velocities and coherent JT |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2310389 |
Moderator Summary#2 on Rel-18 CSI enhancements: Round 1 |
Moderator (Samsung) |
| R1-2310390 |
Moderator Summary for Tuesday offline on Rel-18 CSI enhancements |
Moderator (Samsung) |
| R1-2310444 |
Moderator Summary#3 on Rel-18 CSI enhancements: Round 2 |
Moderator (Samsung) |
| R1-2310445 |
Moderator Summary for Wednesday offline on Rel-18 CSI enhancements |
Moderator (Samsung) |
| 8.1.3.1 |
Increased number of orthogonal DMRS ports |
|
| R1-2308926 |
Maintenance of DMRS enhancement in Rel.18 |
Huawei, HiSilicon |
| R1-2308962 |
Remaining Details on Rel-18 DMRS Enhancements |
InterDigital, Inc. |
| R1-2308976 |
Remaining issues on increased number of orthogonal DMRS ports |
Spreadtrum Communications |
| R1-2309016 |
Maintenance on DMRS enhancement for UL/DL MU-MIMO and 8 Tx UL SU-MIMO |
ZTE, China Telecom |
| R1-2309063 |
Maintenance on DMRS enhancements |
vivo |
| R1-2309209 |
DM-RS Enhancements for Rel-18 |
Intel Coporation |
| R1-2309211 |
On increased number of orthogonal DMRS ports for MU-MIMO and 8 Tx UL SU-MIMO |
Ericsson |
| R1-2309255 |
On DMRS Enhancement |
Google |
| R1-2309275 |
Remaining issues on increased number of orthogonal DMRS ports |
NEC |
| R1-2309318 |
Maintenance on increased number of orthogonal DMRS ports |
Lenovo |
| R1-2309364 |
Views on DMRS enhancements |
Samsung |
| R1-2309427 |
Discussion on the remaining issues about DMRS enhancement |
xiaomi |
| R1-2309496 |
Remaining issues on DL and UL DMRS enhancement |
CATT |
| R1-2309566 |
Remaining issues on DMRS enhancement for Rel-18 MIMO |
OPPO |
| R1-2309638 |
Discussion on remaining issues of PTRS for 8Tx UL transmission |
Fujitsu |
| R1-2309662 |
Remaining issues on increased number of orthogonal DMRS ports |
CMCC |
| R1-2309766 |
Discussions on increased number of orthogonal DMRS ports |
Ruijie Network Co. Ltd |
| R1-2309823 |
Views on remaining issues for DMRS enhancement |
Apple |
| R1-2309918 |
Maintenance of Rel-18 UL and DL DMRS Enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2309964 |
Maintenance on increased number of orthogonal DMRS ports |
Sharp |
| R1-2310025 |
Remaining issues on DMRS enhancements |
NTT DOCOMO, INC. |
| R1-2310130 |
Design for increased number of orthogonal DMRS ports |
Qualcomm Incorporated |
| R1-2310278 |
FL summary on DMRS#1 |
Moderator (NTT DOCOMO) |
| R1-2310279 |
FL summary on DMRS#2 |
Moderator (NTT DOCOMO) |
| R1-2310280 |
FL summary on DMRS#3 |
Moderator (NTT DOCOMO) |
| R1-2310466 |
Additional information of text proposals for R18 DMRS |
Moderator (NTT DOCOMO) |
| 8.1.3.2 |
SRS enhancement targeting TDD CJT and 8 TX operation |
|
| R1-2308927 |
Maintenance of SRS enhancement for TDD CJT and UL 8Tx operation in Rel-18 |
Huawei, HiSilicon |
| R1-2308933 |
SRS enhancements for TDD CJT and 8TX operation |
FUTUREWEI |
| R1-2308963 |
Remaining Details on Rel-18 SRS Enhancements |
InterDigital, Inc. |
| R1-2308977 |
Remaining issues on SRS enhancement targeting TDD CJT and 8 TX operation |
Spreadtrum Communications |
| R1-2309017 |
Maintenance on SRS enhancement targeting TDD CJT and 8 TX operation |
ZTE |
| R1-2309064 |
Maintenance on SRS enhancements |
vivo |
| R1-2309165 |
SRS enhancement targeting TDD CJT and 8 TX operation |
LG Electronics |
| R1-2309252 |
Remaining issues for SRS enhancements targeting TDD CJT and 8 TX operation |
Ericsson |
| R1-2309256 |
On SRS Enhancement |
Google |
| R1-2309276 |
Remaining issues on SRS enhancement |
NEC |
| R1-2309319 |
Maintenance on SRS enhancement |
Lenovo |
| R1-2309365 |
Views on SRS enhancements |
Samsung |
| R1-2309428 |
Maintenance on SRS enhancements |
xiaomi |
| R1-2309497 |
Maintenance on SRS enhancement |
CATT |
| R1-2309567 |
Remaining issues on SRS enhancement targeting TDD CJT and 8 TX operation |
OPPO |
| R1-2309663 |
Remaining issues on SRS enhancement targeting TDD CJT and 8 TX operation |
CMCC |
| R1-2309767 |
Discussions on SRS enhancement targeting TDD CJT and 8 TX operation |
Ruijie Network Co. Ltd |
| R1-2309824 |
Views on Rel-18 MIMO SRS enhancement |
Apple |
| R1-2309919 |
Maintenance of SRS enhancement for TDD CJT and 8Tx operation |
Nokia, Nokia Shanghai Bell |
| R1-2309965 |
Maintenance on SRS enhancement targeting TDD CJT and 8 TX operation |
Sharp |
| R1-2310026 |
Remaining issues on SRS enhancement |
NTT DOCOMO, INC. |
| R1-2310131 |
SRS enhancement for TDD CJT and 8 Tx operation |
Qualcomm Incorporated |
| R1-2310223 |
Remaining issues on SRS enhancement targeting TDD CJT and 8 TX operation |
KDDI Corporation |
| R1-2310330 |
FL Summary #1 on SRS enhancements |
Moderator (FUTUREWEI) |
| R1-2310331 |
FL Summary #2 on SRS enhancements |
Moderator (FUTUREWEI) |
| R1-2310332 |
FL Summary #3 on SRS enhancements |
Moderator (FUTUREWEI) |
| R1-2310644 |
Draft LS on coherence between PUSCH and 8-ports SRS with partial dropping |
Moderator (Qualcomm) |
| R1-2310645 |
LS on coherence between PUSCH and 8-ports SRS with partial dropping |
Moderator (Qualcomm) |
| 8.1.4.1 |
UL precoding indication for multi-panel transmission |
|
| R1-2308928 |
Maintenance of UL precoding indication for multi-panel transmission |
Huawei, HiSilicon |
| R1-2308952 |
Discussions on the remaining issue on UL precoding indication for multi-panel transmission |
New H3C Technologies Co., Ltd. |
| R1-2308964 |
Remaining Details on Rel-18 MPUE Uplink Transmission |
InterDigital, Inc. |
| R1-2308978 |
Remaining issues on UL precoding indication for multi-panel transmission |
Spreadtrum Communications |
| R1-2309018 |
Maintenance on UL precoding indication for multi-panel transmission |
ZTE |
| R1-2309065 |
Maintenance on UL precoding indication for multi-panel transmission |
vivo |
| R1-2309203 |
UL precoding indication for multi-panel transmission |
Intel Coporation |
| R1-2309253 |
Remaining issues for UL precoding indication for multi-panel transmission |
Ericsson |
| R1-2309257 |
On Simultaneous Multi-Panel Transmission |
Google |
| R1-2309284 |
Remaining issues on UL precoding indication for multi-panel transmission |
NEC |
| R1-2309320 |
Maintenance on UL precoding indication for multi-panel transmission |
Lenovo |
| R1-2309366 |
Views on UL precoding indication for STxMP |
Samsung |
| R1-2309429 |
Maintenance on multi-panel uplink transmission |
xiaomi |
| R1-2309498 |
Discussion of remaining issues on UL precoding indication for multi-panel transmission |
CATT |
| R1-2309568 |
Remaining issues of UL precoding indication for multi-panel transmission |
OPPO |
| R1-2309639 |
Correction on PTRS-DMRS association for configured grant Type 1 PUSCH |
Fujitsu |
| R1-2309664 |
Remaining issues on UL precoding indication for multi-panel transmission |
CMCC |
| R1-2309716 |
Remaining issues of UL precoding indication for multi-panel transmission |
Transsion Holdings |
| R1-2309768 |
Discussions on UL precoding indication for multi-panel transmission |
Ruijie Network Co. Ltd |
| R1-2309825 |
Remaining issues on multi-panel simultaneous transmissions |
Apple |
| R1-2309920 |
Maintenance of precoder Indication for Multi-Panel UL Transmission |
Nokia, Nokia Shanghai Bell |
| R1-2310027 |
Remaining issues on multi-panel transmission |
NTT DOCOMO, INC. |
| R1-2310068 |
Maintenance on UL multi-panel transmission |
Sharp |
| R1-2310132 |
Simultaneous multi-panel transmission |
Qualcomm Incorporated |
| R1-2310281 |
Summary #1 on Rel-18 STxMP |
Moderator (OPPO) |
| R1-2310282 |
Summary #2 on Rel-18 STxMP |
Moderator (OPPO) |
| R1-2310283 |
Summary #3 on Rel-18 STxMP |
Moderator (OPPO) |
| 8.1.4.2 |
SRI/TPMI enhancement for enabling 8 TX UL transmission |
|
| R1-2308929 |
Maintenance of SRI/TPMI enhancement for enabling 8 TX UL transmission |
Huawei, HiSilicon |
| R1-2308965 |
Remaining Details on Rel-18 8TX UE Operation |
InterDigital, Inc. |
| R1-2308966 |
FL Summary SRI/TPMI Enhancements; Preparatory |
Moderator (InterDigital, Inc.) |
| R1-2308967 |
FL Summary SRI/TPMI Enhancements; First Round |
Moderator (InterDigital, Inc.) |
| R1-2308968 |
FL Summary SRI/TPMI Enhancements; Second Round |
Moderator (InterDigital, Inc.) |
| R1-2308969 |
FL Summary SRI/TPMI Enhancements; Third Round |
Moderator (InterDigital, Inc.) |
| R1-2308970 |
FL Summary SRI/TPMI Enhancements; Forth Round |
Moderator (InterDigital, Inc.) |
| R1-2308971 |
Summary of Discussion and Agreements in RAN1#114bis |
Moderator (InterDigital, Inc.) |
| R1-2308979 |
Remaining issues on SRI/TPMI enhancement for enabling 8 TX UL transmission |
Spreadtrum Communications |
| R1-2309019 |
Maintenance on SRI/TPMI enhancement for enabling 8 TX UL transmission |
ZTE |
| R1-2309066 |
Maintenance on enabling 8 TX UL transmission |
vivo |
| R1-2309166 |
SRI/TPMI enhancement for enabling 8 TX UL transmission |
LG Electronics |
| R1-2309258 |
On SRI/TPMI Indication for 8Tx Transmission |
Google |
| R1-2309277 |
Remaining issues on SRI/TPMI enhancement |
NEC |
| R1-2309321 |
Maintenance on SRI/TPMI enhancement for enabling 8TX UL transmission |
Lenovo |
| R1-2309367 |
Views on TPMI/SRI enhancements for 8Tx UL transmission |
Samsung |
| R1-2309430 |
Enhancements on 8Tx uplink transmission |
xiaomi |
| R1-2309499 |
Remaining issues on enhancement of SRI/TPMI for 8TX UL transmission |
CATT |
| R1-2309569 |
Remaining issues on SRI TPMI enhancement for 8 TX UL transmission |
OPPO |
| R1-2309640 |
Discussion on remaining issues for 8Tx UL transmission |
Fujitsu |
| R1-2309665 |
Remaining issues on SRI/TPMI enhancement for enabling 8 TX UL transmission |
CMCC |
| R1-2309726 |
Discussion on Full Power Mode for 8 TX UL Transmission |
FGI |
| R1-2309769 |
Discussions on SRI/TPMI enhancement for enabling 8 TX UL transmission |
Ruijie Network Co. Ltd |
| R1-2309826 |
Maintenance on SRI/TPMI enhancement for enabling 8 TX UL transmission |
Apple |
| R1-2309921 |
Maintenance of UL enhancements for enabling 8Tx UL transmission |
Nokia, Nokia Shanghai Bell |
| R1-2309966 |
8 Tx SRI/TPMI Corrections |
Ericsson |
| R1-2310028 |
Remaining issues on 8 TX UL transmission |
NTT DOCOMO, INC. |
| R1-2310069 |
Maintenance on 8 TX UL transmission |
Sharp |
| R1-2310133 |
Enhancements for 8 Tx UL transmissions |
Qualcomm Incorporated |
| R1-2310227 |
Remaining issues on SRI/TPMI enhancement for enabling 8 TX UL transmission |
KDDI Corporation |
| R1-2310287 |
8 Tx SRI/TPMI Corrections |
Ericsson |
| 8.2 |
Maintenance on NR Sidelink Evolution |
|
| R1-2309586 |
Higher layer parameters list for Rel-18 NR sidelink evolution WI |
OPPO, Huawei, HiSilicon, LG Electronics |
| R1-2310541 |
Session notes for 8.2 (Maintenance on NR sidelink evolution) |
Ad-Hoc Chair (Huawei) |
| 8.2.1.1 |
Channel access mechanism |
|
| R1-2308839 |
Remaining issues for Channel Access Mechanism for SL-U |
Nokia, Nokia Shanghai Bell |
| R1-2308884 |
Maintenance of channel access mechanism and resource allocation for sidelink operation over unlicensed spectrum |
Huawei, HiSilicon |
| R1-2308944 |
Discussion on channel access mechanism for sidelink on unlicensed spectrum |
FUTUREWEI |
| R1-2308980 |
Remaining issues on channel access mechanism for sidelink on unlicensed spectrum |
Spreadtrum Communications |
| R1-2309067 |
Remaining issues on channel access mechanism for sidelink on unlicensed spectrum |
vivo |
| R1-2309112 |
Remaining issues for channel access mechanism for SL-U |
ZTE, Sanechips |
| R1-2309235 |
Remaining issues on channel access mechanism for sidelink on unlicensed spectrum |
LG Electronics |
| R1-2309281 |
Remaining Issues on Channel Access of Sidelink on Unlicensed Spectrum |
NEC |
| R1-2309368 |
Remaining issues on channel access mechanism |
Samsung |
| R1-2309452 |
Remaining details on SL-U channel access mechanism |
xiaomi |
| R1-2309519 |
Remaining issues on channel access mechanism for sidelink on unlicensed spectrum |
CATT, CICTCI |
| R1-2309587 |
On maintenance of SL-U channel access mechanism and resource allocation |
OPPO |
| R1-2309666 |
Maintenance on channel access mechanism for sidelink on unlicensed spectrum |
CMCC |
| R1-2309699 |
Remaining issues on channel access mechanism for sidelink on unlicensed spectrum |
Lenovo |
| R1-2309701 |
Remaining issues on channel access mechanism for sidelink on unlicensed spectrum |
ETRI |
| R1-2309717 |
Remaining issues of channel access mechanism for sidelink in unlicensed spectrum |
Transsion Holdings |
| R1-2309827 |
On remaining issues for sidelink channal access procedure for unlicensed spectrum |
Apple |
| R1-2309868 |
Sidelink channel access on unlicensed spectrum |
Panasonic |
| R1-2309932 |
Channel Access Mechanism for SL-U |
ITL |
| R1-2309934 |
Remaining issues for channel access on SL-U |
InterDigital, Inc. |
| R1-2309994 |
Discussion on remaining issue for channel access mechanism |
MediaTek Inc. |
| R1-2310029 |
Remaining issue on channel access mechanism in SL-U |
NTT DOCOMO, INC. |
| R1-2310102 |
Remaining issues on Channel access mechanism for NR sidelink evolution |
Sharp |
| R1-2310134 |
Channel Access Mechanism for Sidelink on Unlicensed Spectrum |
Qualcomm Incorporated |
| R1-2310212 |
On maintenance of channel access mechanism for SL-U |
Ericsson |
| R1-2310231 |
Remaining issues on channel access mechanism for SL-U |
WILUS Inc. |
| R1-2310288 |
FL summary #1 for AI 8.2.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2310289 |
FL summary #2 for AI 8.2.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2310290 |
FL summary #3 for AI 8.2.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2310291 |
FL summary #4 for AI 8.2.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2310292 |
FL summary #5 for AI 8.2.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2310293 |
FL summary for AI 8.2.1.1: SL-U channel access mechanism (EOM) |
Moderator (OPPO) |
| R1-2310433 |
Draft reply LS on SL RB set index and LBT failure indication for PSFCH |
Moderator (OPPO) |
| R1-2310434 |
Reply LS on SL RB set index and LBT failure indication for PSFCH |
RAN1, OPPO |
| R1-2310599 |
FL summary #6 for AI 8.2.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2310600 |
FL summary #7 for AI 8.2.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| 8.2.1.2 |
Physical channel design framework |
|
| R1-2308840 |
Remaining issues for Physical Channel Design Framework for SL-U |
Nokia, Nokia Shanghai Bell |
| R1-2308885 |
Maintenance of physical channel design for sidelink operation over unlicensed spectrum |
Huawei, HiSilicon |
| R1-2308945 |
Discussion on physical channel design for sidelink on unlicensed spectrum |
FUTUREWEI |
| R1-2308981 |
Remaining issues on Physical channel design for sidelink on unlicensed spectrum |
Spreadtrum Communications |
| R1-2309068 |
Remaining issues on physical channel design framework for sidelink on unlicensed spectrum |
vivo |
| R1-2309113 |
Remaining issues for physical layer structures and procedures for SL-U |
ZTE, Sanechips |
| R1-2309236 |
Remaining issues on physical channel design framework for sidelink on unlicensed spectrum |
LG Electronics |
| R1-2309272 |
Remaining issues on physical channel design framework |
NEC |
| R1-2309369 |
Remaining issues on physical channel design framework |
Samsung |
| R1-2309453 |
Remaining details on SL-U physical channel structures and procedures |
xiaomi |
| R1-2309520 |
Remaining issues on physical channel design framework for sidelink on unlicensed spectrum |
CATT, CICTCI |
| R1-2309588 |
On maintenance of SL-U PHY channel designs and procedures |
OPPO |
| R1-2309667 |
Maintenance on physical channel design framework for sidelink on unlicensed spectrum |
CMCC |
| R1-2309700 |
Remaining issues on physical layer design framework for sidelink on unlicensed spectrum |
Lenovo |
| R1-2309702 |
Remaining issues on physical channel design framework for SL-U |
ETRI |
| R1-2309718 |
Remaining issues of physical channel design for sidelink in unlicensed spectrum |
Transsion Holdings |
| R1-2309828 |
On Remaining Issues of Sidelink Physical Channel Design Framework for Unlicensed Spectrum |
Apple |
| R1-2309870 |
Physical channel design for sidelink on unlicensed spectrum |
Panasonic |
| R1-2309879 |
Discussion on channel design for SL-U |
ASUSTeK |
| R1-2309935 |
Remaining issues for SL U physical layer design |
InterDigital, Inc. |
| R1-2309995 |
Discussion on remaining issue for physical channel design framework |
MediaTek Inc. |
| R1-2310030 |
Remaining issue on channel design framework in SL-U |
NTT DOCOMO, INC. |
| R1-2310103 |
Remaining issues on physical channel design framework for NR sidelink evolution on unlicensed spectrum |
Sharp |
| R1-2310135 |
Physical Channel Design for Sidelink on Unlicensed Spectrum |
Qualcomm Incorporated |
| R1-2310213 |
On maintenance of physical channel design framework for SL-U |
Ericsson |
| R1-2310232 |
Remaining issues on PHY channel design for SL-U |
WILUS Inc. |
| R1-2310350 |
FL summary#1 for AI 8.2.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2310351 |
FL summary#2 for AI 8.2.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2310352 |
FL summary#3 for AI 8.2.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2310353 |
FL summary#4 for AI 8.2.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2310354 |
FL summary#5 for AI 8.2.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2310355 |
FL summary#6 for AI 8.2.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2310580 |
FL summary#7 for AI 8.2.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2310594 |
Draft LS on PSFCH power control |
Huawei, HiSilicon |
| R1-2310595 |
LS on PSFCH power control |
RAN1, Huawei |
| 8.2.2 |
Co-channel coexistence for LTE sidelink and NR sidelink |
|
| R1-2308841 |
Remaining issues for Co-channel Coexistence for LTE Sidelink and NR Sidelink |
Nokia, Nokia Shanghai Bell |
| R1-2308886 |
Maintenance of co-channel coexistence for LTE sidelink and NR sidelink |
Huawei, HiSilicon |
| R1-2308982 |
Remaining issues on co-channel coexistence for LTE sidelink and NR sidelink |
Spreadtrum Communications |
| R1-2309069 |
Remaining issues on co-channel coexistence for LTE sidelink and NR sidelink |
vivo |
| R1-2309114 |
Maintenance on co-channel coexistence for LTE sidelink and NR sidelink |
ZTE, Sanechips |
| R1-2309237 |
Remaining issues on co-channel coexistence for LTE sidelink and NR sidelink |
LG Electronics |
| R1-2309239 |
FL Summary #1 for AI 8.2.2: Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (LG Electronics) |
| R1-2309240 |
FL Summary #2 for AI 8.2.2: Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (LG Electronics) |
| R1-2309241 |
FL Summary #3 for AI 8.2.2: Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (LG Electronics) |
| R1-2309370 |
Remaining issues on co-channel coexistence for LTE sidelink and NR sidelink |
Samsung |
| R1-2309521 |
Remaining issues on co-channel coexistence for LTE sidelink and NR sidelink |
CATT, CICTCI |
| R1-2309589 |
On maintenance of co-channel coexistence for LTE and NR SL |
OPPO |
| R1-2309703 |
Remaining issues on co-channel coexistence for LTE sidelink and NR sidelink |
ETRI |
| R1-2309778 |
Dynamic co-channel coexistence for LTE sidelink and NR sidelink |
TOYOTA InfoTechnology Center |
| R1-2309829 |
On Remaining Issues of Co-channel Coexistence |
Apple |
| R1-2309936 |
Remaining issues for Co-channel coexistence between LTE sidelink and NR sidelink |
InterDigital, Inc. |
| R1-2310031 |
Maintenance on co-channel coexistence for LTE sidelink and NR sidelink |
NTT DOCOMO, INC. |
| R1-2310104 |
Remaining issues on co-channel coexistence for LTE sidelink and NR sidelink |
Sharp |
| R1-2310136 |
Co-channel Coexistence Between LTE SL and NR SL |
Qualcomm Incorporated |
| R1-2310190 |
On remaining co-channel coexistence issues for LTE sidelink and NR sidelink |
Mitsubishi Electric RCE |
| R1-2310214 |
On maintenance of co-channel coexistence between LTE sidelink and NR sidelink |
Ericsson |
| R1-2310233 |
Remaining issue on co-channel coexistence for LTE sidelink and NR sidelink |
WILUS Inc. |
| R1-2310534 |
FL Summary #4 for AI 8.2.2: Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (LG Electronics) |
| 8.2.3 |
Sidelink CA operation |
|
| R1-2308842 |
Remaining issues for Sidelink Carrier Aggregation for NR |
Nokia, Nokia Shanghai Bell |
| R1-2309070 |
Remaining issues on Rel-18 sidelink CA |
vivo |
| R1-2309115 |
Remaining issues for sidelink CA operation |
ZTE, Sanechips |
| R1-2309238 |
Remaining issues on sidelink CA operation |
LG Electronics |
| R1-2309242 |
FL Summary #1 for AI 8.2.3: Sidelink CA operation |
Moderator (LG Electronics) |
| R1-2309243 |
FL Summary #2 for AI 8.2.3: Sidelink CA operation |
Moderator (LG Electronics) |
| R1-2309244 |
FL Summary #3 for AI 8.2.3: Sidelink CA operation |
Moderator (LG Electronics) |
| R1-2309371 |
Remaining issues on sidelink CA operation |
Samsung |
| R1-2309454 |
Remaining details on Sidelink CA operation |
xiaomi |
| R1-2309522 |
Maintenance on NR sidelink CA operation |
CATT, CICTCI |
| R1-2309562 |
Enhanced SL Operation in FR2 |
Quectel |
| R1-2309590 |
On maintenance of carrier aggregation in NR Sidelink evolution |
OPPO |
| R1-2309704 |
Remaining issues on sidelink CA operation |
ETRI |
| R1-2309744 |
Maintenance of sidelink CA operation |
Huawei, HiSilicon |
| R1-2309937 |
Remaining issues for Sidelink CA operation |
InterDigital, Inc. |
| R1-2310032 |
Maintenance on sidelink CA operation |
NTT DOCOMO, INC. |
| R1-2310105 |
Remaining issues on Carrier Aggregation for NR sidelink evolution |
Sharp |
| R1-2310137 |
NR Sidelink Carrier Aggregation |
Qualcomm Incorporated |
| R1-2310215 |
On maintenance of sidelink carrier aggregation operation |
Ericsson |
| R1-2310535 |
FL Summary #4 for AI 8.2.3: Sidelink CA operation |
Moderator (LG Electronics) |
| 8.3 |
Maintenance on Expanded and Improved NR Positioning |
|
| R1-2309194 |
Higher layer parameters for Rel-18 Expanded and Improved NR Positioning |
Rapporteur (Intel Corporation) |
| R1-2310542 |
Session notes for 8.3 (Maintenance on expanded and improved NR positioning) |
Ad-Hoc Chair (Huawei) |
| R1-2310592 |
Discussion on list of higher layer parameters on Rel-18 WI on expanded and improved NR positioning |
Rapporteur (Intel Corporation) |
| R1-2310593 |
RAN1 agreements for Rel-18 WI on Expanded and Improved NR Positioning |
Rapporteur (Intel Corporation) |
| 8.3.1 |
Sidelink positioning |
|
| R1-2310400 |
FLS#1 on reply LS on SL positioning MAC agreements |
Moderator (Huawei) |
| R1-2310401 |
Draft reply LS on SL positioning MAC agreements |
Moderator (Huawei) |
| R1-2310402 |
Reply LS on SL positioning MAC agreements |
RAN1, Huawei |
| R1-2310536 |
FLS#2 on reply LS on SL positioning MAC agreements |
Moderator (Huawei) |
| 8.3.1.1 |
SL positioning reference signal |
|
| R1-2308843 |
Remaining issues for design of SL positioning reference signal SL PRS |
Nokia, Nokia Shanghai Bell |
| R1-2308874 |
Maintenance of SL-PRS |
Huawei, HiSilicon |
| R1-2308983 |
Remaining issues on SL positioning reference signal |
Spreadtrum Communications |
| R1-2309071 |
Remaining issues on SL positioning reference signal |
vivo |
| R1-2309195 |
Remaining issues on SL Positioning Reference Signals |
Intel Coporation |
| R1-2309219 |
Maintenance on SL positioning reference signal |
ZTE |
| R1-2309245 |
Remaining issues on SL positioning reference signal |
LG Electronics |
| R1-2309287 |
Remaining issues on SL positioning reference signal |
NEC |
| R1-2309372 |
Maintenance on SL Positioning Reference Signal |
Samsung |
| R1-2309455 |
Remaining details on SL positioning reference signal |
xiaomi |
| R1-2309523 |
Maintenance on SL positioning reference signal |
CATT, CICTCI |
| R1-2309539 |
Maintenance on sidelink positioning reference signal |
ASUSTeK |
| R1-2309591 |
Remaining issues on SL positioning reference signal |
OPPO |
| R1-2309668 |
Maintenance on SL positioning reference signal |
CMCC |
| R1-2309771 |
Discussions on SL positioning reference signal |
Ruijie Network Co. Ltd |
| R1-2309780 |
Discussion on SL positioning reference signal design |
TOYOTA InfoTechnology Center |
| R1-2309795 |
Remaining issues on SL-PRS design and power control for SL-PRS |
InterDigital, Inc. |
| R1-2309830 |
On SL positioning reference signal |
Apple |
| R1-2309881 |
Remaining issues on SL positioning reference signal |
Sharp |
| R1-2309903 |
Remaining issues on SL Positioning Reference Signal Design |
Sony |
| R1-2309945 |
SL PRS Design Maintenance Aspects |
Lenovo |
| R1-2310089 |
Maintenance for SL-PRS design |
MediaTek Korea Inc. |
| R1-2310138 |
Maintenance for SL PRS Signal Design |
Qualcomm Incorporated |
| R1-2310195 |
Remaining issues on SL positioning reference signal design |
Ericsson |
| R1-2310333 |
FL summary #1 on SL positioning reference signal |
Moderator (Intel Corporation) |
| R1-2310334 |
FL summary #2 on SL positioning reference signal |
Moderator (Intel Corporation) |
| R1-2310335 |
FL summary #3 on SL positioning reference signal |
Moderator (Intel Corporation) |
| 8.3.1.2 |
Measurements and reporting for SL positioning |
|
| R1-2308844 |
Remaining issues for measurements and reporting for SL positioning |
Nokia, Nokia Shanghai Bell |
| R1-2308875 |
Maintenance of SL measurements |
Huawei, HiSilicon |
| R1-2308984 |
Remaining issues on measurements and reporting for SL positioning |
Spreadtrum Communications |
| R1-2309072 |
Remaining issues on measurements and reporting for SL positioning |
vivo |
| R1-2309196 |
Remaining issues on SL Positioning Measurements and Reporting |
Intel Coporation |
| R1-2309220 |
Maintenance on SL positioning measurements and reporting |
ZTE |
| R1-2309246 |
Remaining issues on measurements and reporting for SL positioning |
LG Electronics |
| R1-2309293 |
Discussion on SL positioning measurements and reporting |
BUPT |
| R1-2309373 |
Maintenance on Measurements and Reporting for SL Positioning |
Samsung |
| R1-2309456 |
Remaining details on measurements and reporting for SL positioning |
xiaomi |
| R1-2309524 |
Maintenance on measurements and reporting for SL positioning |
CATT, CICTCI |
| R1-2309592 |
Remaining issues on measurements and reporting for SL positioning |
OPPO |
| R1-2309669 |
Maintenance on measurements and reporting for SL positioning |
CMCC |
| R1-2309781 |
Discussion on SL measurements and reporting |
TOYOTA InfoTechnology Center |
| R1-2309796 |
Remaining issues on measurement and reporting for SL positioning |
InterDigital, Inc. |
| R1-2309831 |
On Measurements and reporting for SL positioning |
Apple |
| R1-2309904 |
Remaining Issues on SL positioning methods and measurements |
Sony |
| R1-2309946 |
Measurement and Reporting Maintenance Discussion |
Lenovo |
| R1-2310139 |
Maintenance for SL Positioning Measurements |
Qualcomm Incorporated |
| R1-2310196 |
Remaining issues on measurements and reporting for SL positioning |
Ericsson |
| R1-2310342 |
Summary #1 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| R1-2310343 |
Summary #2 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| R1-2310344 |
Summary #3 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| 8.3.1.3 |
Resource allocation for SL positioning reference signal |
|
| R1-2308845 |
Remaining issues for resource allocation for SL positioning reference signal SL PRS |
Nokia, Nokia Shanghai Bell |
| R1-2308876 |
Maintenance of SL-PRS resource allocation |
Huawei, HiSilicon |
| R1-2308946 |
Discussion on resource allocation for SL PRS |
FUTUREWEI |
| R1-2308985 |
Remaining issues on resource allocation for SL positioning reference signal |
Spreadtrum Communications |
| R1-2309073 |
Remaining issues on resource allocation for SL positioning reference signal |
vivo |
| R1-2309197 |
Remaining issues on resource allocation for SL positioning |
Intel Coporation |
| R1-2309221 |
Maintenance on resource allocation for SL positioning reference signal |
ZTE |
| R1-2309247 |
Remaining issues on resource allocation for SL positioning reference signal |
LG Electronics |
| R1-2309288 |
Remaining issues on resource allocation for SL positioning reference signal |
NEC |
| R1-2309374 |
Maintenance on Resource Allocation for SL Positioning Reference Signal |
Samsung |
| R1-2309457 |
Remaining details on resource allocation for SL positioning reference signal |
xiaomi |
| R1-2309525 |
Maintenance on resource allocation for SL positioning reference signal |
CATT, CICTCI |
| R1-2309540 |
Remaining issues on Resource allocation for SL PRS |
ASUSTeK |
| R1-2309550 |
Remaining issues on resource allocation for SL PRS |
China Telecom |
| R1-2309593 |
Remaining issues on resource allocation for SL positioning reference signal |
OPPO |
| R1-2309670 |
Maintenance on resource allocation for SL positioning reference signal |
CMCC |
| R1-2309782 |
Discussion on SL positioning resource allocation |
TOYOTA InfoTechnology Center |
| R1-2309789 |
Remaining Issues on Resource Allocation for SL-PRS |
Panasonic |
| R1-2309797 |
Remaining issues of SL PRS resource allocation |
InterDigital, Inc. |
| R1-2309832 |
On Resource allocation for SL positioning reference signal |
Apple |
| R1-2309874 |
Remaining Issues on Resource Allocation for Sidelink Positioning |
Continental Automotive |
| R1-2309882 |
Remaining issues on resource allocation for SL positioning reference signal |
Sharp |
| R1-2309905 |
Remaining Issues on resource allocation for SL positioning |
Sony |
| R1-2309947 |
Remaining aspects for SL Positioning Resource Allocation |
Lenovo |
| R1-2310140 |
Maintenance for SL PRS Resource Allocation |
Qualcomm Incorporated |
| R1-2310197 |
Remaining issues on resource allocation for SL positioning reference signal |
Ericsson |
| R1-2310241 |
Discussions on resource allocation for sidelink positioning |
ITL |
| R1-2310396 |
Moderator Summary #0 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| R1-2310414 |
Moderator Summary #1 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| R1-2310483 |
Moderator Summary #2 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| R1-2310601 |
Moderator Summary #3 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| 8.3.2 |
NR DL and UL carrier phase positioning |
|
| R1-2308877 |
Maintenance of CPP |
Huawei, HiSilicon |
| R1-2308955 |
Remaining issues on NR DL and UL carrier phase positioning |
Nokia, Nokia Shanghai Bell |
| R1-2308986 |
Remaining issues on NR DL and UL carrier phase positioning |
Spreadtrum Communications |
| R1-2309074 |
Remaining issues on carrier phase positioning |
vivo |
| R1-2309198 |
Remaining details on NR DL and UL Carrier Phase Positioning |
Intel Coporation |
| R1-2309222 |
Maintenance on carrier phase positioning |
ZTE |
| R1-2309326 |
Remaining issues on carrier phase positioning in NR |
LG Electronics |
| R1-2309375 |
Maintenance on NR DL and UL Carrier Phase Positioning |
Samsung |
| R1-2309458 |
Remaining issues on NR DL and UL carrier phase positioning |
xiaomi |
| R1-2309526 |
Maintenance on NR DL and UL carrier phase positioning |
CATT |
| R1-2309575 |
Remaining Issues of NR carrier phase positioning |
OPPO |
| R1-2309671 |
Maintenance on carrier phase positioning |
CMCC |
| R1-2309798 |
Remaining issues for positioning based on NR carrier phase measurement |
InterDigital, Inc. |
| R1-2309833 |
On NR DL and UL carrier phase positioning |
Apple |
| R1-2309938 |
Discussions on NR DL and UL carrier phase positioning |
Ruijie Network Co. Ltd |
| R1-2309948 |
DL/UL CPP Maintenance Discussion |
Lenovo |
| R1-2310033 |
Remaining issues on NR DL and UL carrier phase positioning |
NTT DOCOMO, INC. |
| R1-2310090 |
Maintenance for carrier phase positioning |
MediaTek Korea Inc. |
| R1-2310141 |
Maintenance for NR Carrier Phase Positioning |
Qualcomm Incorporated |
| R1-2310198 |
Remaining issues on NR DL and UL carrier phase positioning |
Ericsson |
| R1-2310284 |
FL Summary #1 for maintenance on NR DL and UL carrier phase positioning |
Moderator (CATT) |
| R1-2310285 |
FL Summary #2 for maintenance on NR DL and UL carrier phase positioning |
Moderator (CATT) |
| R1-2310286 |
FL Summary #3 for maintenance on NR DL and UL carrier phase positioning |
Moderator (CATT) |
| 8.3.3 |
LPHAP (Low Power High Accuracy Positioning) |
|
| R1-2308878 |
Maintenance of LPHAP |
Huawei, HiSilicon |
| R1-2308956 |
Remaining issues on LPHAP |
Nokia, Nokia Shanghai Bell |
| R1-2309075 |
Remaining issues on low power high accuracy positioning |
vivo |
| R1-2309223 |
Maintenance on low power high accuracy positioning |
ZTE |
| R1-2309286 |
Remaining issues on Low Power High Accuracy Positioning |
NEC |
| R1-2309336 |
Discussion on Low Power High Accuracy Positioning |
Quectel |
| R1-2309376 |
Maintenance on Low Power High Accuracy Positioning |
Samsung |
| R1-2309527 |
Maintenance on low power high accuracy positioning |
CATT |
| R1-2309577 |
Remaining issue of low power high accuracy positioning |
OPPO |
| R1-2309672 |
Maintenance on low power high accuracy positioning |
CMCC |
| R1-2309799 |
Remaining issues on Low Power High Accuracy Positioning (LPHAP) techniques |
InterDigital, Inc. |
| R1-2309834 |
On Low Power High Accuracy Positioning |
Apple |
| R1-2309906 |
Remaining Issues on LPHAP |
Sony |
| R1-2310034 |
Remaining issues on low power high accuracy positioning |
NTT DOCOMO, INC. |
| R1-2310142 |
Maintenance on LPHAP Positioning |
Qualcomm Incorporated |
| R1-2310199 |
Remaining issues on Low Power High Accuracy Positioning |
Ericsson |
| R1-2310318 |
Summary #1 for low power high accuracy positioning |
Moderator (CMCC) |
| R1-2310319 |
Summary #2 for low power high accuracy positioning |
Moderator (CMCC) |
| R1-2310320 |
Summary #3 for low power high accuracy positioning |
Moderator (CMCC) |
| 8.3.4 |
Bandwidth aggregation for positioning measurements |
|
| R1-2308879 |
Maintenance of positioning with BW aggregation |
Huawei, HiSilicon, China Telecom, China Unicom |
| R1-2308957 |
Remaining issues on bandwidth aggregation for positioning measurements |
Nokia, Nokia Shanghai Bell |
| R1-2308987 |
Remaining issues on bandwidth aggregation for positioning measurements |
Spreadtrum Communications |
| R1-2309076 |
Remaining issues on bandwidth aggregation for positioning measurements |
vivo |
| R1-2309107 |
Discussions on Carrier Aggregation for NR Positioning |
BUPT |
| R1-2309199 |
Remaining issues on Bandwidth Aggregation for Positioning |
Intel Coporation |
| R1-2309224 |
Maintenance on BW aggregation for positioning |
ZTE |
| R1-2309227 |
Summary #1 for BW aggregation positioning |
Moderator (ZTE) |
| R1-2309228 |
Summary #2 for BW aggregation positioning |
Moderator (ZTE) |
| R1-2309229 |
Summary #3 for BW aggregation positioning |
Moderator (ZTE) |
| R1-2309327 |
Remaining issues on Bandwidth aggregation for positioning measurements |
LG Electronics |
| R1-2309377 |
Maintenance on Bandwidth Aggregation for Positioning Measurements |
Samsung |
| R1-2309459 |
Remaining issues on bandwidth aggregation for positioning measurement |
xiaomi |
| R1-2309528 |
Maintenance on bandwidth aggregation for positioning measurements |
CATT |
| R1-2309576 |
Remaining Issues of bandwidth aggregation for positioning measurement |
OPPO |
| R1-2309673 |
Maintenance on BW aggregation for positioning measurements |
CMCC |
| R1-2309800 |
Remaining issues on bandwidth aggregation for positioning measurements |
InterDigital, Inc. |
| R1-2309835 |
On Bandwidth aggregation for positioning measurements |
Apple |
| R1-2310035 |
Remaining issues on bandwidth aggregation for positioning measurements |
NTT DOCOMO, INC. |
| R1-2310143 |
Maintenance on Bandwidth aggregation for Positioning |
Qualcomm Incorporated |
| R1-2310200 |
Remaining issues on Bandwidth aggregation for positioning measurements |
Ericsson |
| R1-2310477 |
Draft LS on PRS bandwidth aggregation |
Moderator (ZTE) |
| R1-2310478 |
LS on PRS bandwidth aggregation |
RAN1, ZTE |
| 8.3.5 |
Positioning for RedCap UEs |
|
| R1-2308880 |
Maintenance of RedCap positioning |
Huawei, HiSilicon |
| R1-2308943 |
On remaining open issues in RedCap UE positioning |
FUTUREWEI |
| R1-2308958 |
Remaining issues on Positioning for RedCap UEs |
Nokia, Nokia Shanghai Bell |
| R1-2308988 |
Remaining issues on positioning for RedCap UEs |
Spreadtrum Communications |
| R1-2309077 |
Remaining issues on positioning for RedCap UEs |
vivo |
| R1-2309200 |
Remaining issues on Positioning for RedCap UEs |
Intel Coporation |
| R1-2309225 |
Maintenance on Positioning for RedCap UEs |
ZTE |
| R1-2309289 |
Remaining issues of positioning for RedCap UEs |
NEC |
| R1-2309328 |
Remaining issues on positioning support for RedCap UEs |
LG Electronics |
| R1-2309378 |
Maintenance on Positioning for RedCap UEs |
Samsung |
| R1-2309529 |
Maintenance on positioning for RedCap UEs |
CATT |
| R1-2309578 |
Remaining issue of positioning for RedCap UEs |
OPPO |
| R1-2309674 |
Maintenance on RedCap UE positioning |
CMCC |
| R1-2309801 |
Remaining issues on positioning for RedCap UEs |
InterDigital, Inc. |
| R1-2309836 |
On Positioning for RedCap UEs |
Apple |
| R1-2309907 |
Remaining Issues on Positioning for RedCap UEs |
Sony |
| R1-2310036 |
Remaining issues on positioning for RedCap UEs |
NTT DOCOMO, INC. |
| R1-2310091 |
Maintenance for positioning for RedCap UE |
MediaTek Korea Inc. |
| R1-2310144 |
Maintenance on Positioning for Reduced Capabilities UEs |
Qualcomm Incorporated |
| R1-2310201 |
Remaining issues on Positioning for RedCap UEs |
Ericsson |
| R1-2310429 |
Feature Lead summary #1 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2310430 |
Feature Lead summary #2 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2310431 |
Feature Lead summary #3 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2310688 |
Final Feature Lead summary for Positioning for RedCap UEs |
Moderator (Ericsson) |
| 8.4 |
Maintenance on Enhanced Support of Reduced Capability NR device |
|
| R1-2310329 |
RAN1 agreements for Rel-18 NR RedCap |
Rapporteur (Ericsson) |
| R1-2310543 |
Session notes for 8.4 (Maintenance on enhanced support of reduced capability NR device) |
Ad-hoc Chair (CMCC) |
| 8.4.1 |
UE complexity reduction |
|
| R1-2308896 |
Maintenance of Rel-18 RedCap |
Huawei, HiSilicon |
| R1-2308939 |
Discussion on R18 RedCap |
FUTUREWEI |
| R1-2308989 |
Maintenance on enhanced support of RedCap devices |
Spreadtrum Communications |
| R1-2309078 |
Remaining issues on further UE complexity reduction |
vivo |
| R1-2309177 |
Discussion on further UE complexity reduction |
ZTE, Sanechips |
| R1-2309301 |
Remaining issues of further UE complexity reduction for eRedCap |
LG Electronics |
| R1-2309379 |
Remaining issues on further UE complexity reduction for eRedCap |
Samsung |
| R1-2309460 |
Discussion on further complexity reduction for eRedCap UEs |
xiaomi |
| R1-2309530 |
Remaining issues of Rel-18 RedCap |
CATT |
| R1-2309541 |
MBS for eRedCap |
Panasonic |
| R1-2309551 |
Remaining issues on UE complexity reduction for eRedCap UEs |
China Telecom |
| R1-2309611 |
Further consideration on reduced UE complexity |
OPPO |
| R1-2309675 |
Maintenance on further complexity reduction for eRedCap |
CMCC |
| R1-2309719 |
Remaining issues on UE complexity reduction |
Transsion Holdings |
| R1-2309724 |
Remaining Issues for eRedCap |
Nokia, Nokia Shanghai Bell |
| R1-2309837 |
Further RedCap UE complexity reduction |
Apple |
| R1-2309877 |
Maintenance on Rel-18 RedCap UE |
NEC |
| R1-2309883 |
Remaining issues on UE complexity reduction |
Sharp |
| R1-2309974 |
Maintenance on eRedCap complexity reduction |
MediaTek Inc. |
| R1-2310037 |
Maintenance on further UE complexity reduction for eRedCap |
NTT DOCOMO, INC. |
| R1-2310145 |
Remaining issues for UE complexity reduction for eRedCap |
Qualcomm Incorporated |
| R1-2310226 |
Clarification of random access for Rel-18 eRedCap |
Ericsson |
| R1-2310230 |
Remaining issues on eRedCap UE complexity reduction |
Sony |
| R1-2310240 |
On further complexity reduction of NR UE |
Nordic Semiconductor ASA |
| R1-2310326 |
FL summary #1 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2310327 |
FL summary #2 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2310328 |
FL summary #3 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2310567 |
Agreed 38.213 TPs for Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2310568 |
FL summary #4 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| 8.5 |
Maintenance on Network Energy Savings for NR |
|
| R1-2310576 |
RRC parameter list for Rel-18 network energy savings post 114bis |
Moderator (Huawei) |
| 8.5.1 |
Techniques in spatial and power domains |
|
| R1-2308893 |
Maintenance of CSI enhancements for NES |
Huawei, HiSilicon |
| R1-2308948 |
Techniques in spatial and power domains |
Nokia, Nokia Shanghai Bell |
| R1-2308990 |
Remaining issues on techniques in spatial and power domains |
Spreadtrum Communications |
| R1-2309079 |
Remaining issues on NES techniques in spatial and power domain |
vivo |
| R1-2309178 |
Discussion on NES techniques in spatial and power domains |
ZTE, Sanechips |
| R1-2309192 |
Maintenance issues of enhancements on NES spatial and power domain operations |
Intel Coporation |
| R1-2309261 |
Network Energy Saving in Spatial and Power Domain |
Google |
| R1-2309290 |
Remaining issues on techniques in spatial and power domains |
CEWiT |
| R1-2309294 |
Remaining issues on network energy saving techniques in spatial and power domains |
NEC |
| R1-2309302 |
Remaining issues of NES techniques in spatial and power domains |
LG Electronics |
| R1-2309311 |
Discussion on Remaining issues of NES |
FUTUREWEI |
| R1-2309380 |
Remaining issues on NES techniques in spatial and power domains |
Samsung |
| R1-2309461 |
Remaining issues on NES techniques in spatial and power domains |
xiaomi |
| R1-2309531 |
Network Energy Saving techniques in spatial and power domain |
CATT |
| R1-2309552 |
Remaining issues on SD and PD NES techniques |
China Telecom |
| R1-2309596 |
Discussion on remaining issue for techniques in spatial and power domains |
OPPO |
| R1-2309647 |
Remaining details on NW energy saving techniques in spatial and power domains |
Fujitsu |
| R1-2309676 |
Remaining issues on spatial and power domains enhancements for network energy saving |
CMCC |
| R1-2309720 |
Remaining issues of NES techniques in spatial and power domains |
Transsion Holdings |
| R1-2309838 |
On remaining issues for spatial and power domain enhancements to support network energy saving |
Apple |
| R1-2309894 |
Correction on spatial adaptation |
ASUSTeK |
| R1-2309940 |
Remaining issues on NES techniques in spatial and power domains |
InterDigital, Inc. |
| R1-2309942 |
Spatial and power domain adaptation for network energy saving |
Panasonic |
| R1-2309949 |
Maintenance on Network energy saving techniques in spatial and power domains |
Lenovo |
| R1-2310007 |
Maintenance on NES techniques in spatial and power domains |
MediaTek Inc. |
| R1-2310038 |
Maintenance of spatial and power domain enhancements for NW energy savings |
NTT DOCOMO, INC. |
| R1-2310094 |
Maintenance of NW energy saving techniques in spatial and power domains |
Ericsson |
| R1-2310146 |
Remaining aspects of spatial and power domain adaptation |
Qualcomm Incorporated |
| R1-2310307 |
FL summary#1 for SD and PD adaptation for R18 NES |
Moderator (Huawei) |
| R1-2310308 |
FL summary#2 for SD and PD adaptation for R18 NES |
Moderator (Huawei) |
| R1-2310309 |
FL summary#3 for SD and PD adaptation for R18 NES |
Moderator (Huawei) |
| R1-2310310 |
FL summary#4 for SD and PD adaptation for R18 NES |
Moderator (Huawei) |
| R1-2310574 |
FL summary#5 for SD and PD adaptation for R18 NES |
Moderator (Huawei) |
| R1-2310575 |
Final FL summary for SD and PD adaptation for R18 NES |
Moderator (Huawei) |
| R1-2310577 |
SP-CSI reporting for network energy savings |
Huawei |
| R1-2310578 |
SP-CSI reporting for network energy savings |
RAN1, Huawei |
| 8.5.2 |
Enhancements on cell DTX/DRX mechanism |
|
| R1-2308894 |
Maintenance of Cell DTX/DRX for NES |
Huawei, HiSilicon |
| R1-2308949 |
Enhancements on cell DTX/DRX mechanism |
Nokia, Nokia Shanghai Bell |
| R1-2308991 |
Remaining issues on enhancements on cell DTX/DRX mechanism |
Spreadtrum Communications |
| R1-2309080 |
Remaining issues on enhancements on cell DTX/DRX mechanism |
vivo |
| R1-2309179 |
Discussion on cell DTX/DRX |
ZTE, Sanechips |
| R1-2309262 |
Network Energy Saving on Cell DTX and DRX |
Google |
| R1-2309291 |
Enhancements on cell DTX/DRX mechanism |
CEWiT |
| R1-2309296 |
Remaining issues on cell DTX/DRX configuration for Network Energy Saving |
NEC |
| R1-2309303 |
Remaining issues of cell DTX/DRX mechanism |
LG Electronics |
| R1-2309312 |
DCI 2_9 for Cell DTX/DTX |
FUTUREWEI |
| R1-2309381 |
Remaining issues on cell DTX/DRX mechanism |
Samsung |
| R1-2309462 |
Discussions on cell DTX-DRX for network energy saving |
xiaomi |
| R1-2309532 |
DTX/DRX for network Energy Saving |
CATT |
| R1-2309553 |
Remaining issues on cell DTX/DRX mechanism |
China Telecom |
| R1-2309597 |
Discussion on remaining issue for enhancements on cell DTX/DRX mechanism |
OPPO |
| R1-2309648 |
Remaining details on cell DTX/DRX mechanism |
Fujitsu |
| R1-2309677 |
Remaining issues on cell DTX/DRX mechanism |
CMCC |
| R1-2309705 |
Remaining issues on cell DTX/DRX mechanism |
ETRI |
| R1-2309721 |
Remaining issues on enhancement on cell DTXDRX mechanism |
Transsion Holdings |
| R1-2309839 |
On remaining issues for cell DTX/DRX mechanism |
Apple |
| R1-2309893 |
Correction on cell DTX |
ASUSTeK |
| R1-2309941 |
Remaining issues on cell DTX/DRX mechanism |
InterDigital, Inc. |
| R1-2309943 |
Cell DTX/DRX enhancement for network energy saving |
Panasonic |
| R1-2309950 |
Maintenance on enhancements on cell DTX/DRX mechanism |
Lenovo |
| R1-2310008 |
Maintenance on cell DTX/DRX mechanism |
MediaTek Inc. |
| R1-2310039 |
Maintenance of enhancements on Cell DTX/DRX mechanism |
NTT DOCOMO, INC. |
| R1-2310095 |
Maintenance for cell DTX/DRX |
Ericsson |
| R1-2310147 |
Remaining aspects of cell DTX and DRX |
Qualcomm Incorporated |
| R1-2310243 |
Issues on Cell DTX/DRX |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2310336 |
Summary of maintenance issues for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2310337 |
Discussion summary #1 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2310338 |
Discussion summary #2 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2310452 |
Discussion summary #3 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2310453 |
Discussion summary #4 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2310454 |
Discussion summary #5 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2310475 |
Draft LS on cell DTX/DRX operations |
Moderator (Intel Corporation) |
| R1-2310476 |
LS on cell DTX/DRX operations |
RAN1, Intel Corporation |
| 8.6 |
Maintenance on XR Enhancements for NR |
|
| R1-2309081 |
PDCCH monitoring resumption after NACK |
vivo |
| R1-2310501 |
Draft Reply LS on XR capacity enhancements |
MediaTek |
| R1-2310502 |
Reply LS on XR capacity enhancements |
RAN1, MediaTek |
| 8.6.1 |
XR-specific capacity enhancements |
|
| R1-2308882 |
Maintenance of CG enhancements for XR capacity |
Huawei, HiSilicon |
| R1-2308936 |
Discussion on remaining issues of XR-specific capacity enhancements |
FUTUREWEI |
| R1-2308992 |
Remaining issues on XR-specific capacity enhancements |
Spreadtrum Communications |
| R1-2309082 |
Remaining issue on XR specific capacity enhancements |
vivo |
| R1-2309180 |
Discussion on remaining issues of XR |
ZTE, Sanechips |
| R1-2309273 |
Remaining issues on XR-specific capacity enhancements |
NEC |
| R1-2309297 |
XR-specific capacity enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2309304 |
Remaining issues on XR-specific capacity enhancements |
LG Electronics |
| R1-2309382 |
Maintenance issues on XR |
Samsung |
| R1-2309463 |
Remaining issues on XR-specific capacity enhancements |
xiaomi |
| R1-2309533 |
Design of Multiple CG Occasions and unused CG occasion feedback |
CATT |
| R1-2309620 |
Discussion on XR specific capacity enhancements |
OPPO |
| R1-2309678 |
Maintenance on XR enhancements for NR |
CMCC |
| R1-2309732 |
XR specific capacity enhancements |
TCL |
| R1-2309788 |
Remaining issues on UTO-UCI and HARQ-ACK collision handling |
Sharp |
| R1-2309840 |
Remaining issues in XR-specific capacity enhancements |
Apple |
| R1-2309908 |
Remaining Issues on XR capacity enhancements |
Sony |
| R1-2309939 |
Remaining issues on XR-specific capacity enhancements |
InterDigital, Inc. |
| R1-2310002 |
Remaining issues on XR enhancements |
MediaTek Inc. |
| R1-2310148 |
Maintenance on XR Enhancements |
Qualcomm Incorporated |
| R1-2310255 |
On Maintenance of XR enhancements for NR |
Ericsson |
| R1-2310424 |
Moderator Summary#1 - Maintenance of XR Enhancements |
Moderator (Ericsson) |
| R1-2310425 |
Moderator Summary#2 - Maintenance of XR Enhancements |
Moderator (Ericsson) |
| R1-2310426 |
Moderator Summary#3 - Maintenance of XR Enhancements |
Moderator (Ericsson) |
| R1-2310427 |
Moderator Summary#4 - Maintenance of XR Enhancements |
Moderator (Ericsson) |
| 8.7 |
Maintenance on Further NR Mobility Enhancements |
|
| R1-2310545 |
Session notes for 8.7 (Maintenance on further NR mobility enhancements) |
Ad-Hoc Chair (CMCC) |
| R1-2310676 |
Rel-18 RRC parameters for NR mobility enhancement WI for RAN1 114bis |
Rapporteur (Apple) |
| 8.7.1 |
L1 enhancements for inter-cell beam management |
|
| R1-2308889 |
Maintenance of L1 enhancements for inter-cell beam management |
Huawei, HiSilicon |
| R1-2308934 |
Discussion on remaining issues of L1 enhancements for inter-cell beam management |
FUTUREWEI |
| R1-2308993 |
Remaining issues on L1 enhancements for inter-cell beam management |
Spreadtrum Communications |
| R1-2309020 |
Maintenance on L1 enhancements for inter-cell beam management |
ZTE |
| R1-2309083 |
L1 enhancements for L1/L2-triggered mobility |
vivo |
| R1-2309109 |
FL plan on L1 enhancements for LTM at RAN1#114-bis |
Moderator (Fujitsu, MediaTek) |
| R1-2309110 |
FL summary 1 on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu, MediaTek) |
| R1-2309111 |
FL summary 2 on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu, MediaTek) |
| R1-2309161 |
Maintenance of L1 enhancements to inter-cell beam management |
Ericsson |
| R1-2309216 |
FL plan on L1 enhancements for LTM at RAN1#114-bis |
Moderator (Fujitsu, MediaTek) |
| R1-2309295 |
Remaining issues on L1 enhancements for inter-cell beam management |
NEC |
| R1-2309322 |
Remaining issues on L1 enhancements for inter-cell beam management |
Lenovo |
| R1-2309383 |
Remaining details on L1 enhancements for inter-cell beam management |
Samsung |
| R1-2309464 |
Discussion on remaining issue about L1 enhancements for LTM |
xiaomi |
| R1-2309534 |
Maintenance on L1 enhancements for inter-cell beam management |
CATT |
| R1-2309579 |
Remaining Issues of Inter-cell beam management enhancement |
OPPO |
| R1-2309649 |
Remaining issues on L1 enhancements for inter-cell beam management |
Fujitsu |
| R1-2309679 |
Remaining issues on L1 enhancements for inter-cell beam management |
CMCC |
| R1-2309727 |
Discussion on L1 enhancements for inter-cell beam management |
FGI |
| R1-2309733 |
Remaining Issues on Layer-1 Enhancements for L1/L2-triggered Mobility |
Nokia, Nokia Shanghai Bell |
| R1-2309739 |
Remaining issues on L1 enhancement for LTM |
Panasonic |
| R1-2309786 |
Discussion on L1 enhancements for inter-cell beam management |
Google |
| R1-2309841 |
L1 enhancements to inter-cell beam management |
Apple |
| R1-2309876 |
Remaining issues on L1 enhancements for inter-cell beam management |
KDDI Corporation |
| R1-2309953 |
Remaining issues on L1 enhancements |
InterDigital, Inc. |
| R1-2309982 |
Remaining issues on L1 enhancements for inter-cell beam management |
MediaTek Inc. |
| R1-2310040 |
Remaining issues on L1 enhancements for inter-cell mobility |
NTT DOCOMO, INC. |
| R1-2310149 |
L1 Enhancements for Inter-Cell Beam Management |
Qualcomm Incorporated |
| R1-2310642 |
FL summary 3 on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu, MediaTek) |
| R1-2310643 |
Final FL summary on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu, MediaTek) |
| 8.7.2 |
Timing advance management to reduce latency |
|
| R1-2308890 |
Maintenance of timing advance management to reduce latency |
Huawei, HiSilicon |
| R1-2308935 |
Network assisted UE TA determination with high accuracy |
FUTUREWEI |
| R1-2308994 |
Remaining issues on timing advance management to reduce latency |
Spreadtrum Communications |
| R1-2309021 |
Maintenance on TA management to reduce latency |
ZTE |
| R1-2309084 |
TA management for L1/L2-triggered mobility |
vivo |
| R1-2309162 |
Maintenance of TA management for LTM |
Ericsson |
| R1-2309323 |
Remaining issue of timing advancement management for L1L2 mobility |
Lenovo |
| R1-2309384 |
Remaining issues on candidate cell TA management for NR L1/L2 mobility enhancement |
Samsung |
| R1-2309535 |
Remaining issues on TA management to reduce latency |
CATT |
| R1-2309580 |
Remaining Issues of Timing Advance Management |
OPPO |
| R1-2309680 |
Remaining issues on timing advance management to reduce latency |
CMCC |
| R1-2309728 |
Remaining issues on TA management for LTM |
FGI |
| R1-2309734 |
Remaining Issues on Timing Advance Management for L1/L2-triggered Mobility |
Nokia, Nokia Shanghai Bell |
| R1-2309787 |
Discussion on timing advance management to reduce latency |
Google |
| R1-2309842 |
Timing advance management for L1/L2 Mobility |
Apple |
| R1-2309954 |
Remaining details on timing advance management |
InterDigital, Inc. |
| R1-2310041 |
Remaining issues on TA enhancements for inter-cell mobility |
NTT DOCOMO, INC. |
| R1-2310070 |
Discussion on TA management to reduce latency |
CAICT |
| R1-2310150 |
TA management to reduce latency for L1/L2 based mobility |
Qualcomm Incorporated |
| R1-2310360 |
Moderator summary on timing advance management for LTM: Round 1 |
Moderator (CATT) |
| R1-2310441 |
Moderator summary on timing advance management for LTM: Round 2 |
Moderator (CATT) |
| R1-2310506 |
Moderator summary on timing advance management for LTM: Round 3 |
Moderator (CATT) |
| 8.8 |
Maintenance on Further NR Coverage Enhancements |
|
| R1-2310546 |
Session notes for 8.8 (Maintenance on further NR coverage enhancements) |
Ad-Hoc Chair (CMCC) |
| 8.8.1 |
PRACH coverage enhancements |
|
| R1-2308899 |
Maintenance of PRACH coverage enhancements |
Huawei, HiSilicon |
| R1-2308953 |
Discussions on the remaining issue on PRACH coverage enhancements |
New H3C Technologies Co., Ltd. |
| R1-2308995 |
Remaining issues on PRACH coverage enhancements |
Spreadtrum Communications |
| R1-2309085 |
Discussions on remaining issues of PRACH coverage enhancements |
vivo |
| R1-2309132 |
Discussion on PRACH coverage enhancements |
ZTE |
| R1-2309187 |
Remaining issues on PRACH coverage enhancement |
Intel Coporation |
| R1-2309278 |
Maintenance on PRACH coverage enhancement |
NEC |
| R1-2309329 |
Remaining issues on PRACH coverage enhancements |
LG Electronics |
| R1-2309385 |
PRACH coverage enhancements |
Samsung |
| R1-2309465 |
Discussion on PRACH coverage enhancements |
xiaomi |
| R1-2309536 |
Remaining issues on PRACH coverage enhancements |
CATT |
| R1-2309554 |
Remaining issues on PRACH coverage enhancement |
China Telecom |
| R1-2309612 |
Remaining issues on PRACH coverage enhancements |
OPPO |
| R1-2309633 |
Discussion on PRACH coverage enhancements |
Panasonic |
| R1-2309650 |
Remaining issues on PRACH coverage enhancement |
Fujitsu |
| R1-2309681 |
Remaining issues on PRACH coverage enhancements |
CMCC |
| R1-2309706 |
PRACH coverage enhancements |
ETRI |
| R1-2309731 |
PRACH coverage enhancements |
TCL |
| R1-2309772 |
Discussions on PRACH coverage enhancements |
Ruijie Network Co. Ltd |
| R1-2309804 |
Remaining issues of PRACH coverage enhancements |
Lenovo |
| R1-2309843 |
Discussion on PRACH coverage enhancements |
Apple |
| R1-2309909 |
Remaining issues on multiple PRACH transmissions for PRACH coverage enhancement |
Sony |
| R1-2309924 |
Remaining issues on PRACH coverage enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2309958 |
Remaining issues on PRACH coverage enhancements |
InterDigital, Inc. |
| R1-2309967 |
Discussion on PRACH Coverage Enhancement |
Ericsson |
| R1-2310001 |
Remaining issues on PRACH coverage enhancements |
MediaTek Inc. |
| R1-2310042 |
Remaining issues on PRACH coverage enhancements |
NTT DOCOMO, INC. |
| R1-2310071 |
Remaining issues on PRACH coverage enhancements |
Quectel |
| R1-2310106 |
Remaining issues on multiple PRACH transmissions for Rel-18 CovEnh |
Sharp |
| R1-2310151 |
PRACH Coverage Enhancements |
Qualcomm Incorporated |
| R1-2310303 |
FL Summary #1 on remaining issues for PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2310304 |
FL Summary #2 on remaining issues for PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2310305 |
FL Summary #3 on remaining issues for PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2310486 |
Collection of endorsed TPs in AI 8.8.1 PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2310579 |
FL Summary #4 on remaining issues for PRACH coverage enhancements |
Moderator (China Telecom) |
| 8.8.2 |
Power domain enhancements |
|
| R1-2308900 |
Discussion on coverage enhancement in power domain |
Huawei, HiSilicon |
| R1-2309086 |
Discussions on remaining issues of power domain enhancements |
vivo |
| R1-2309188 |
Remaining issues on power domain enhancement |
Intel Coporation |
| R1-2309386 |
Power domain enhancements |
Samsung |
| R1-2309466 |
Maintenance on power domain enhancements |
xiaomi |
| R1-2309537 |
RAN1 impact for power domain enhancement |
CATT |
| R1-2309555 |
Remaining issues on power domain enhancements |
China Telecom |
| R1-2309613 |
Remaining issues on of power domain enhancements |
OPPO |
| R1-2309682 |
Remaining issues on power domain enhancements |
CMCC |
| R1-2309914 |
Discussion on power domain enhancements |
ZTE |
| R1-2309925 |
Remaining issues on power domain enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2309968 |
Power Domain Enhancement Maintenance |
Ericsson |
| R1-2310152 |
Power-domain enhancements |
Qualcomm Incorporated |
| R1-2310300 |
FL summary of power domain enhancements (AI 8.8.2) |
Moderator (Nokia) |
| R1-2310301 |
FL summary #2 of power domain enhancements (AI 8.8.2) |
Moderator (Nokia) |
| R1-2310302 |
Final FL summary of power domain enhancements (AI 8.8.2) |
Moderator (Nokia) |
| R1-2310489 |
Draft reply LS on RAN1 impacts regarding enhancements to realize increasing UE power high limit for CA and DC |
Nokia |
| R1-2310518 |
Reply LS on RAN1 impacts regarding enhancements to realize increasing UE power high limit for CA and DC |
RAN1, Nokia |
| 8.8.3 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
|
| R1-2308901 |
Maintenance of dynamic waveform switching for coverage enhancement |
Huawei, HiSilicon |
| R1-2308996 |
Remaining issues on dynamic switching between DFT-S-OFDM and CP-OFDM |
Spreadtrum Communications |
| R1-2309087 |
Discussions on remaining issues of dynamic waveform switching |
vivo |
| R1-2309133 |
Discussion on dynamic waveform switching |
ZTE |
| R1-2309189 |
Remaining issues on dynamic waveform switching |
Intel Coporation |
| R1-2309279 |
Maintenance on dynamic switching between DFT-S-OFDM and CP-OFDM |
NEC |
| R1-2309330 |
Remaining issues on dynamic waveform switching for NR coverage enhancement |
LG Electronics |
| R1-2309387 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
Samsung |
| R1-2309467 |
Maintenance on dynamic switching between DFT-s-OFDM and CP-OFDM |
xiaomi |
| R1-2309538 |
Remaining issues on dynamic switching between DFT-S-OFDM and CP-OFDM |
CATT |
| R1-2309556 |
Remaining issues on dynamic waveform switching between DFT-s-OFDM and CP-OFDM |
China Telecom |
| R1-2309614 |
Issues on dynamic switching between DFT-S-OFDM and CP-OFDM |
OPPO |
| R1-2309630 |
Discussion on the remaining issues for dynamic waveform switching |
Panasonic |
| R1-2309683 |
Remaining issues on dynamic switching between DFT-S-OFDM and CP-OFDM |
CMCC |
| R1-2309707 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
ETRI |
| R1-2309722 |
Remaining issues of dynamic switching between DFT-S-OFDM and CP-OFDM |
Transsion Holdings |
| R1-2309729 |
Remaining issues on dynamic switching between DFT-S-OFDM and CP-OFDM |
Lenovo |
| R1-2309783 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
InterDigital, Inc. |
| R1-2309844 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
Apple |
| R1-2309910 |
Maintenance Issues on DWS Configuration and PHR reporting |
Sony |
| R1-2309926 |
Remaining issues on dynamic switching between DFT-s-OFDM and CP-OFDM |
Nokia, Nokia Shanghai Bell |
| R1-2309969 |
Discussion on Dynamic UL Waveform Switching |
Ericsson |
| R1-2310043 |
Remaining issues on dynamic switching between DFT-S-OFDM and CP-OFDM |
NTT DOCOMO, INC. |
| R1-2310107 |
Remaining issues on dynamic waveform switching for Rel-18 CovEnh |
Sharp |
| R1-2310153 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
Qualcomm Incorporated |
| R1-2310248 |
Summary #1 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| R1-2310249 |
Summary #2 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| R1-2310456 |
Summary #3 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| R1-2310457 |
Summary #4 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| R1-2310499 |
Collection of endorsed TPs in AI 8.8.3 Dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| 8.9 |
Maintenance on NR Support for Dedicated Spectrum Less than 5MHz for FR1 |
|
| R1-2309902 |
Introduction of NR support for dedicated spectrum less than 5MHz for FR1 to TS 38.300 |
Nokia (Rapporteur) |
| R1-2310548 |
Session notes for 8.9 (Maintenance on NR support for dedicated spectrum less than 5MHz for FR1) |
Ad-Hoc Chair (CMCC) |
| 8.9.1 |
Enhancements to operate NR on dedicated spectrum less than 5 MHz |
|
| R1-2308897 |
Maintenance of dedicated spectrum less than 5 MHz |
Huawei, HiSilicon |
| R1-2308941 |
Discussion on less than 5 MHz dedicated spectrum |
FUTUREWEI |
| R1-2308997 |
Maintenance on enhancements to operate NR on dedicated spectrum |
Spreadtrum Communications |
| R1-2309134 |
Remaining issues on dedicated spectrum less than 5 MHz |
ZTE |
| R1-2309248 |
NR support for below 5 MHz BW |
Nokia, Nokia Shanghai Bell |
| R1-2309305 |
Remaining issues of enhancements for dedicated spectrum less than 5 MHz |
LG Electronics |
| R1-2309388 |
Remaining issues for enhancements to operate NR on dedicated spectrum less than 5 MHz |
Samsung |
| R1-2309653 |
Open issues of dedicated spectrum less than 5MHz for FR1 |
TD Tech, Chengdu TD Tech |
| R1-2309805 |
Remaining issues on dedicated spectrum less than 5 MHz |
Lenovo |
| R1-2309845 |
NR support of spectrum less than 5MHz for FR1 |
Apple |
| R1-2309889 |
Maintenance on NR support of spectrum less than 5MHz for FR1 |
Ericsson |
| R1-2309975 |
Maintenance on dedicated spectrum less than 5MHz |
MediaTek Inc. |
| R1-2310044 |
Remaining issues on enhancements to operate NR on dedicated spectrum less than 5 MHz |
NTT DOCOMO, INC. |
| R1-2310154 |
NR support for dedicated spectrum less than 5MHz for FR1 |
Qualcomm Incorporated |
| R1-2310377 |
Summary#1 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz |
Moderator (Lenovo) |
| R1-2310378 |
Summary#2 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz |
Moderator (Lenovo) |
| R1-2310498 |
Summary#3 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz |
Moderator (Lenovo) |
| R1-2310569 |
Summary on the agreed text proposals for dedicated spectrum less than 5MHz |
Moderator (Lenovo) |
| 8.10 |
Maintenance on Enhancement of NR Dynamic Spectrum Sharing (DSS) |
|
| R1-2310549 |
Session notes for 8.10 (Maintenance on enhancement of NR Dynamic Spectrum Sharing) |
Ad-Hoc Chair (CMCC) |
| 8.10.1 |
NR PDCCH reception in symbols with LTE CRS Res |
|
| R1-2308922 |
Maintenance of NR PDCCH reception in symbols with LTE CRS REs |
Huawei, HiSilicon |
| R1-2309135 |
Maintenance of NR PDCCH reception in symbols with LTE CRS |
ZTE |
| R1-2309622 |
Remaining issues for PDCCH reception in overlapping with LTE CRS |
OPPO |
| R1-2310009 |
Remaining Issues on NR PDCCH Reception in Symbols with LTE CRS REs |
Langbo |
| R1-2310045 |
Maintenance on NR PDCCH reception in symbols with LTE CRS REs |
NTT DOCOMO, INC. |
| R1-2310096 |
Maintenance for reception of NR PDCCH candidates overlapping with LTE CRS REs |
Ericsson |
| R1-2310155 |
NR PDCCH reception in symbols with LTE CRS REs |
Qualcomm Incorporated |
| R1-2310361 |
Moderator Summary#1 for Rel. 18 eDSS |
Moderator (Intel Corporation) |
| R1-2310362 |
Moderator Summary#2 for Rel. 18 eDSS |
Moderator (Intel Corporation) |
| R1-2310363 |
Moderator Summary#3 for Rel. 18 eDSS |
Moderator (Intel Corporation) |
| R1-2310596 |
Endorsed text proposals for TS38.211 and TS38.213 for Rel. 18 eDSS |
Moderator (Intel Corporation) |
| 8.11.1 |
Side control information and NCR behaviour |
|
| R1-2308905 |
Maintenance of side control information and NCR behaviour |
Huawei, HiSilicon |
| R1-2309088 |
Remaining issues on side control information and NCR behaviour |
vivo |
| R1-2309147 |
Remaining issue on side control information and NCR behavior |
ZTE |
| R1-2309331 |
Remaining issues on side control information and NCR behaviour |
LG Electronics |
| R1-2309389 |
Remaining Issues on side control information and NCR behaviour |
Samsung |
| R1-2309431 |
Discussion on remaining issues of NCR |
xiaomi |
| R1-2309500 |
Maintenance on side control information and NCR behaviour for NR Network-Controlled Repeaters |
CATT |
| R1-2309542 |
Remaining issues for side control information and NCR behaviour |
InterDigital, Inc. |
| R1-2309641 |
Remaining issues on side control information and NCR behaviour |
Fujitsu |
| R1-2309684 |
Remaining issues on side control information and NCR behaviour |
CMCC |
| R1-2309708 |
Discussion on NCR maintenance |
ETRI |
| R1-2309774 |
Side-control information and NCR behaviour |
Ericsson |
| R1-2309792 |
Discussion on remaining issues of side control information for NCR |
Lenovo |
| R1-2310046 |
Discussion on Side control information and NCR behavior |
NTT DOCOMO, INC. |
| R1-2310413 |
Summary#1 of maintenance issues on side control information and NCR behavior |
Moderator (ZTE) |
| R1-2310494 |
Summary#2 of maintenance issues on side control information and NCR behavior |
Moderator (ZTE) |
| 8.11.2 |
Other aspects including control plane signalling and procedures relevant to RAN1 |
|
| R1-2308906 |
Maintenance of other aspects for NCR |
Huawei, HiSilicon |
| R1-2309148 |
Remaining issue on other aspects of NCR |
ZTE |
| R1-2309390 |
Remaining Issues on signaling and procedures for network-controlled repeaters |
Samsung |
| R1-2309501 |
Maintenance on other aspects including control plane signalling and procedures relevant to RAN1 for NR Network-Controlled Repeaters |
CATT |
| R1-2309775 |
Control-plane signaling and procedures for NCR |
Ericsson |
| R1-2309846 |
On remaining issues for BFR procedures for backhaul link in NCR |
Apple |
| R1-2310311 |
Summary#1 on other aspects |
Moderator (Fujitsu) |
| 8.12.1 |
Multi-cell PUSCH/PDSCH scheduling with a single DCI |
|
| R1-2308919 |
Maintenance of multi-cell PDSCCH/PUSCH scheduling with a single DCI |
Huawei, HiSilicon |
| R1-2308998 |
Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Spreadtrum Communications |
| R1-2309089 |
Remaining issues on Rel-18 Multi-cell scheduling |
vivo |
| R1-2309136 |
Maintenance of Multi-cell PUSCH/PDSCH scheduling with a single DCI |
ZTE |
| R1-2309171 |
On Rel-18 MC-DCI scheduling |
Nokia, Nokia Shanghai Bell |
| R1-2309306 |
Remaining issues on Multi-cell scheduling with single DCI |
LG Electronics |
| R1-2309391 |
Remaining Issues on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Samsung |
| R1-2309432 |
Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI |
xiaomi |
| R1-2309502 |
Maintenance on Multi-cell PUSCH/PDSCH scheduling with a single DCI |
CATT |
| R1-2309623 |
Remaining issues for multi-cell PUSCH/PDSCH scheduling with a single DCI |
OPPO |
| R1-2309642 |
Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Fujitsu |
| R1-2309685 |
Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI |
CMCC |
| R1-2309698 |
Remaining issues on Rel-18 multi-cell scheduling |
Lenovo |
| R1-2309709 |
Remaining issues on multi-cell PUSCH/PDSCH scheduling |
ETRI |
| R1-2309847 |
On remaining issues for Rel-18 multi-cell scheduling |
Apple |
| R1-2309875 |
Remaining detail on multi-cell scheduling with a single DCI |
ITRI |
| R1-2309972 |
On maintenance for multi-cell scheduling with a single DCI |
MediaTek Inc. |
| R1-2310010 |
Remaining Issues on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Langbo |
| R1-2310047 |
Maintenance on multi-cell PUSCH/PDSCH scheduling with a single DCI |
NTT DOCOMO, INC. |
| R1-2310097 |
Maintenance for single DCI scheduling multiple cells |
Ericsson |
| R1-2310156 |
Multi-cell PUSCH/PDSCH scheduling with a single DCI |
Qualcomm Incorporated |
| R1-2310393 |
Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2310394 |
Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2310395 |
Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2310651 |
Feature lead summary#4 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| 8.12.2 |
Multi-carrier UL Tx switching scheme |
|
| R1-2308920 |
Maintenance of multi-carrier UL Tx switching schemes |
Huawei, HiSilicon |
| R1-2308999 |
Remaining issues on UL Tx switching |
Spreadtrum Communications |
| R1-2309090 |
Remaining issues on Rel-18 UL Tx switching across 3 or 4 bands |
vivo |
| R1-2309137 |
Maintenance of Multi-carrier UL Tx switching scheme |
ZTE |
| R1-2309307 |
Remaining issues on Multi-carrier UL Tx switching scheme |
LG Electronics |
| R1-2309433 |
Remaining issues on multi-carrier UL Tx switching scheme |
xiaomi |
| R1-2309503 |
Maintenance on Multi-carrier UL Tx switching scheme |
CATT |
| R1-2309557 |
Remaining issues on Rel-18 UL Tx switching |
China Telecom |
| R1-2309624 |
Remaining issues on multi-carrier UL Tx switching scheme |
OPPO |
| R1-2309686 |
Remaining issues on multi-carrier UL Tx switching scheme |
CMCC |
| R1-2309848 |
On remaining issues for Rel-18 UL Tx switching |
Apple |
| R1-2309922 |
Remaining issues for R18 multi-carrier UL Tx switching |
MediaTek Inc. |
| R1-2309923 |
On remaining issues of Multi-carrier UL Tx switching CR to 38.214 |
Nokia, Nokia Shanghai Bell |
| R1-2310048 |
Maintenance on multi-carrier UL Tx switching scheme |
NTT DOCOMO, INC. |
| R1-2310157 |
Discussion on Rel-18 UL Tx switching |
Qualcomm Incorporated |
| R1-2310257 |
On Maintenance for Multi-Carrier UL TX switching |
Ericsson |
| R1-2310380 |
Summary of discussion on Multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2310490 |
Summary#2 of discussion on Multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2310491 |
Draft LS on TS38.300 TP for UL Tx switching in Rel-18 |
Moderator (NTT DOCOMO, INC.) |
| R1-2310492 |
LS on TS38.300 TP for UL Tx switching in Rel-18 |
RAN1, NTT DOCOMO |
| R1-2310582 |
Summary#3 of discussion on Multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2310583 |
Draft LS on conditions for triggering switch and descriptions on determination of the length of switching period in specifications |
Moderators (NTT DOCOMO, INC.) |
| R1-2310584 |
LS on conditions for triggering switch and descriptions on determination of the length of switching period in specifications |
RAN1, NTT DOCOMO, INC. |
| R1-2310677 |
Summary#4 of discussion on Multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2310678 |
Draft LS on determination of switching period location in frequency domain based on band priority |
Moderators (NTT DOCOMO, INC.) |
| R1-2310679 |
Response LS on determination of switching period location in frequency domain based on band priority |
RAN1, NTT DOCOMO, INC. |
| 8.13 |
Maintenance on NTN (Non-Terrestrial Networks) Enhancements |
|
| R1-2308863 |
Considerations on the system parameters for FR2-NTN |
THALES |
| R1-2308872 |
R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 |
THALES |
| R1-2309149 |
Discussion on the RAN1 related aspects for NTN above 10 GHz |
ZTE |
| R1-2309333 |
Discussion on RAN4 LS on FR2-NTN PRACH aspects |
LG Electronics |
| R1-2309492 |
Discussion on FR2 issues for NR NTN |
CATT |
| R1-2309543 |
Discussion on the RAN1 impact for NTN above 10GHz |
Beijing Xiaomi Mobile Software |
| R1-2309849 |
Discussion on NTN above 10 GHz |
Apple |
| R1-2309988 |
Discussion on RAN4 LS on the system parameters for NTN above 10 GHz |
MediaTek Inc. |
| R1-2310049 |
Discussion on FR2-NTN for NR NTN |
NTT DOCOMO, INC. |
| R1-2310108 |
Discussions on RAN4 LS on FR2-NTN aspects |
Sharp |
| R1-2310158 |
Power control for RACH-less handover in NR NTN |
Qualcomm Incorporated |
| R1-2310221 |
R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 |
THALES |
| R1-2310412 |
Discussion on RAN4 LS on FR2-NTN aspects |
Moderator (Nokia) |
| R1-2310496 |
Summary of discussion on remaining issues for RACH-less handover |
Moderator (Samsung) |
| R1-2310544 |
Session notes for 8.13 (Maintenance on NTN (Non-Terrestrial Networks) enhancements) |
Ad-Hoc Chair (Huawei) |
| R1-2310564 |
Discussion on RAN4 LS on FR2-NTN aspects, second round |
Moderator (Nokia) |
| R1-2310650 |
Rel-18 Higher Layer Parameters for NR NTN |
Moderator (Thales) |
| R1-2310682 |
Rel-18 Higher Layer Parameters for IoT NTN |
Moderator (MediaTek) |
| R1-2310687 |
RAN1 agreements for Rel-18 WI on NR NTN enhancements up to RAN1#114-bis |
WI rapporteur (Thales) |
| R1-2310689 |
RAN1 agreements for Rel-18 WI on IoT NTN enhancements up to RAN1#114bis |
Moderator (MediaTek) |
| 8.13.1 |
Coverage enhancement for NR NTN |
|
| R1-2308908 |
Maintenance of coverage enhancement for NR NTN |
Huawei, HiSilicon |
| R1-2309091 |
Discussions on remaining issues of coverage enhancements in NR NTN |
vivo |
| R1-2309150 |
Remaining issue on coverage enhancement |
ZTE |
| R1-2309230 |
Remaining issues on coverage enhancement for NR NTN |
Spreadtrum Communications |
| R1-2309250 |
Maintenance of coverage enhancement for NR NTN |
Baicells |
| R1-2309313 |
On coverage enhancements for NR NTN |
Ericsson |
| R1-2309334 |
Remaining issues on coverage enhancement for NR NTN |
LG Electronics |
| R1-2309392 |
Remaining issues on coverage enhancement for NR NTN |
Samsung |
| R1-2309434 |
Discussion on remaining issues on coverage enhancement for NR-NTN |
xiaomi |
| R1-2309504 |
Discussion on remaining issues of UL coverage enhancement for NR NTN |
CATT |
| R1-2309598 |
Discussion on remaining issue for coverage enhancement for NR NTN |
OPPO |
| R1-2309687 |
Remaining issues on coverage enhancement for NR NTN |
CMCC |
| R1-2309710 |
Maintenance of coverage enhancements for NR NTN |
ETRI |
| R1-2309712 |
Remaining issues on coverage enhancement for NR-NTN |
Panasonic |
| R1-2309736 |
Open issues related to coverage enhancements for NR over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2309793 |
Discussion on remaining issues of coverage enhancement for NR NTN |
Lenovo |
| R1-2309850 |
On Remaining Issues of Coverage Enhancement for NR NTN |
Apple |
| R1-2309986 |
Coverage enhancement for NR NTN |
MediaTek Inc. |
| R1-2310050 |
Maintenance of coverage enhancement for NR NTN |
NTT DOCOMO, INC. |
| R1-2310109 |
Remaining issues on coverage enhancement for NR NTN |
Sharp |
| R1-2310159 |
Maintenance on coverage enhancements for NR NTN |
Qualcomm Incorporated |
| R1-2310294 |
Summary #1 on 8.13.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2310295 |
Summary #2 on 8.13.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2310296 |
Summary #3 on 8.13.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| 8.13.2 |
Network verified UE location for NR NTN |
|
| R1-2308862 |
Maintenance on network verified UE location in NR NTN |
THALES |
| R1-2308864 |
Feature Lead Summary #1 on Network verified UE location for NR NTN |
THALES |
| R1-2308865 |
Feature Lead Summary #2 on Network verified UE location for NR NTN |
THALES |
| R1-2308866 |
Feature Lead Summary #3 on Network verified UE location for NR NTN |
THALES |
| R1-2308867 |
Feature Lead Summary #4 on Network verified UE location for NR NTN |
THALES |
| R1-2308909 |
Maintenance of network-verified UE location for NR NTN |
Huawei, HiSilicon |
| R1-2309092 |
Discussions on remaining issues of UE location verification in NR NTN |
vivo |
| R1-2309151 |
Remaining issue on network verified UE location |
ZTE |
| R1-2309393 |
Remaining issues on network verified UE location for NR NTN |
Samsung |
| R1-2309435 |
Discussion on the remaining issues for network verified location for NR-NTN |
xiaomi |
| R1-2309505 |
Discussion on remaining issues on Network verified UE location for NR NTN |
CATT |
| R1-2309599 |
Discussion on remaining issue for network verified UE location for NR NTN |
OPPO |
| R1-2309737 |
Open issues related to network verified UE location for NR over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2309851 |
On Remaining Issues of Network Verified UE Location |
Apple |
| R1-2309987 |
Network verified UE location for NR NTN |
MediaTek Inc. |
| R1-2310051 |
Remaining issue on Network verified UE location for NR NTN |
NTT DOCOMO, INC. |
| R1-2310160 |
Maintenance on network verified UE location for NR NTN |
Qualcomm Incorporated |
| R1-2310236 |
On maintenance of network verified UE location for NR NTN |
Ericsson Limited |
| 8.13.3 |
Disabling of HARQ feedback for IoT NTN |
|
| R1-2308911 |
Maintenance of disabling of HARQ feedback for IoT NTN |
Huawei, HiSilicon |
| R1-2309000 |
Remaining issues on disabling of HARQ feedback for IoT NTN |
Spreadtrum Communications |
| R1-2309172 |
Remaining issue on disabling of HARQ feedback |
ZTE |
| R1-2309280 |
Disabling of HARQ-ACK feedback for IoT NTN |
NEC |
| R1-2309394 |
Remaining issues on disabling of HARQ feedback for IoT NTN |
Samsung |
| R1-2309600 |
Discussion on remaining issue on disabling of HARQ feedback for IoT NTN |
OPPO |
| R1-2309651 |
Maintenance on disabling of HARQ feedback for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R1-2309794 |
Disabling of HARQ feedback for IoT NTN |
Lenovo |
| R1-2309852 |
On Higher Layer Signaling for HARQ Feedback Disabling for IoT NTN |
Apple |
| R1-2309888 |
Maintenance on disabling HARQ feedback for IoT NTN |
Ericsson |
| R1-2309979 |
Remaining issues on disabling of HARQ for IoT NTN |
MediaTek Inc. |
| R1-2310161 |
Disabling HARQ Feedback for IoT-NTN |
Qualcomm Incorporated |
| R1-2310356 |
FLS#1 on disabling of HARQ feedback for IoT NTN |
Moderator (Lenovo) |
| R1-2310615 |
FLS#2 on disabling of HARQ feedback for IoT NTN |
Moderator (Lenovo) |
| 8.13.4 |
Improved GNSS operations for IoT NTN |
|
| R1-2308912 |
Maintenance of improved GNSS operations for IoT NTN |
Huawei, HiSilicon |
| R1-2309001 |
Remaining issues on improved GNSS operations for IoT NTN |
Spreadtrum Communications |
| R1-2309152 |
Remaining issue on improved GNSS operation |
ZTE |
| R1-2309395 |
Remaining issues on improved GNSS operations for IoT NTN |
Samsung |
| R1-2309436 |
Discussion on the remaining issues for the improved GNSS operation for IoT NTN |
xiaomi |
| R1-2309506 |
Discussion on remaining issues of improved GNSS operations for IoT NTN |
CATT |
| R1-2309601 |
Discussion on remaining issue for improved GNSS operation for IoT NTN |
OPPO |
| R1-2309652 |
Maintenance on improved GNSS operations for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R1-2309688 |
Remaining issues on improved GNSS operations for IoT NTN |
CMCC |
| R1-2309853 |
On improved GNSS operations for IoT NTN |
Apple |
| R1-2309980 |
Remaining issues on improved GNSS operations for IoT NTN |
MediaTek Inc. |
| R1-2310162 |
Improved GNSS Operations for IoT-NTN |
Qualcomm Incorporated |
| R1-2310188 |
Improved GNSS operations for IoT NTN |
Nordic Semiconductor ASA |
| R1-2310235 |
On maintenance of improved GNSS operations for IoT NTN |
Ericsson Limited |
| R1-2310297 |
Feature lead summary#1 of AI 8.13.4 on improved GNSS operations |
Moderator (MediaTek) |
| R1-2310298 |
Feature lead summary#2 of AI 8.13.4 on improved GNSS operations |
Moderator (MediaTek) |
| R1-2310299 |
Feature lead summary#3 of AI 8.13.4 on improved GNSS operations |
Moderator (MediaTek) |
| 8.14 |
Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR Air Interface |
|
| R1-2308837 |
Text Proposals to TR 38.843 |
Ericsson |
| R1-2310163 |
Updated TR 38.843 after RAN1#114 |
Qualcomm Incorporated |
| R1-2310540 |
Session notes for 8.14 (Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface) |
Ad-hoc Chair (CMCC) |
| 8.14.1 |
General aspects of AI/ML framework |
|
| R1-2308915 |
Remaining issues on general aspects of AI/ML framework |
Huawei, HiSilicon |
| R1-2308937 |
Discussion on remaining open issues of AI/ML for air-interface general framework |
FUTUREWEI |
| R1-2308954 |
Evaluation on AI/ML for CSI feedback enhancement |
RAN1, Comba |
| R1-2309002 |
Discussion on general aspects of AIML framework |
Spreadtrum Communications |
| R1-2309093 |
Discussions on AI/ML framework |
vivo |
| R1-2309143 |
Discussion on general aspects of common AI PHY framework |
ZTE |
| R1-2309167 |
Remaining issues on AI/ML framework |
LG Electronics |
| R1-2309184 |
Discussion on general aspects of AI/ML framework |
Ericsson |
| R1-2309185 |
General aspects of AI and ML framework for NR air interface |
NVIDIA |
| R1-2309204 |
General aspects of AI/ML framework for NR air interface |
Intel Coporation |
| R1-2309249 |
General aspects of AI/ML framework for NR air interface |
Baicells |
| R1-2309259 |
On General Aspects of AI/ML Framework |
Google |
| R1-2309285 |
Discussion on general aspects of AI ML framework |
NEC |
| R1-2309337 |
Remaining issues on general aspects of AI/ML framework |
Panasonic |
| R1-2309396 |
Samsung's view on the remaining general aspects of AI/ML framework |
Samsung |
| R1-2309437 |
Discussion on the remaining issues of AI/ML framework |
xiaomi |
| R1-2309507 |
On general aspects of AI/ML framework |
CATT |
| R1-2309544 |
Discussions on general aspects of AI/ML framework |
Mavenir |
| R1-2309617 |
On general aspects of AI/ML framework |
OPPO |
| R1-2309643 |
Discussion on general aspects of AI/ML framework |
Fujitsu |
| R1-2309689 |
Discussion on general aspects of AI/ML framework |
CMCC |
| R1-2309723 |
Discussion on general aspects of AI/ML framework |
Continental Automotive |
| R1-2309770 |
Discussions on general aspects of AI/ML framework |
Ruijie Network Co. Ltd |
| R1-2309773 |
Discussion on general aspects of AI/ML framework |
Sharp |
| R1-2309806 |
Considering on system architecture for AI/ML framework deployment |
TCL |
| R1-2309854 |
Discussion on general aspect of AI/ML framework |
Apple |
| R1-2309873 |
Prediction of untransmitted beams in a UE-side AI-ML model |
Rakuten Symphony |
| R1-2309886 |
General aspects of AI/ML framework |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2309911 |
Remaining issues on general AI/ML framework |
Sony |
| R1-2309951 |
On general aspects of AI/ML framework |
Lenovo |
| R1-2309955 |
Discussion on general aspects of AI/ML framework |
InterDigital, Inc. |
| R1-2310052 |
Discussion on general aspects of AI/ML framework |
NTT DOCOMO, INC. |
| R1-2310080 |
General Aspects of AI/ML framework |
AT&T |
| R1-2310183 |
General aspects of AI/ML framework |
Qualcomm Incorporated |
| R1-2310184 |
On Functionality and Model ID -based LCM |
Nokia, Nokia Shanghai Bell |
| R1-2310234 |
On General Aspects of AI/ML Framework |
IIT Kanpur, Indian Institute of Tech (M) |
| R1-2310237 |
Discussions on General Aspects of AI/ML Framework |
Indian Institute of Tech (M), IIT Kanpur |
| R1-2310368 |
Summary#1 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2310369 |
Summary#2 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2310370 |
Draft reply LS on Data Collection Requirements and Assumptions |
Moderator (Qualcomm) |
| R1-2310371 |
Summary#3 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2310372 |
Summary#5 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2310373 |
Summary#6 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2310374 |
Final summary of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2310523 |
Discussion #2 for reply LS on Data Collection Requirements and Assumptions |
Qualcomm Incorporated |
| R1-2310638 |
Draft reply LS on Data Collection Requirements and Assumptions |
Moderator (Qualcomm) |
| R1-2310681 |
Reply LS on Data Collection Requirements and Assumptions |
RAN1, Qualcomm |
| 8.14.2 |
Other aspects on AI/ML for CSI feedback enhancement |
|
| R1-2308873 |
Discussions on AI-CSI |
Ericsson |
| R1-2308916 |
Remaining issues on AI/ML for CSI feedback enhancement |
Huawei, HiSilicon |
| R1-2308938 |
Discussion on remaining open issues for other aspects of AI/ML for CSI feedback enhancement |
FUTUREWEI |
| R1-2309003 |
Discussion on other aspects on AIML for CSI feedback |
Spreadtrum Communications |
| R1-2309094 |
Other aspects on AI/ML for CSI feedback enhancement |
vivo |
| R1-2309144 |
Discussion on other aspects for AI CSI feedback enhancement |
ZTE |
| R1-2309168 |
Remaining issues on AI/ML for CSI enhancement |
LG Electronics |
| R1-2309186 |
AI and ML for CSI feedback enhancement |
NVIDIA |
| R1-2309207 |
Discussion on AI/ML for CSI feedback |
Intel Coporation |
| R1-2309260 |
On Enhancement of AI/ML based CSI |
Google |
| R1-2309271 |
Other aspects on AI/ML for CSI feedback enhancement |
NEC |
| R1-2309397 |
Samsung's view on remaining aspects on AI/ML for CSI feedback enhancement |
Samsung |
| R1-2309438 |
Remaining issues discussion on specification impact for CSI feedback based on AI/ML |
xiaomi |
| R1-2309508 |
On other aspects for AI/ML CSI feedback enhancement |
CATT |
| R1-2309558 |
Discussion on AI/ML for CSI feedback enhancement |
China Telecom |
| R1-2309618 |
On other aspects of AI/ML for CSI feedback enhancement |
OPPO |
| R1-2309631 |
Discussion on AI/ML for CSI feedback enhancement |
Panasonic |
| R1-2309644 |
Views on specification impact for CSI feedback enhancement |
Fujitsu |
| R1-2309690 |
Discussion on other aspects on AI/ML for CSI feedback enhancement |
CMCC |
| R1-2309855 |
Discussion on other aspects of AI/ML for CSI enhancement |
Apple |
| R1-2309869 |
Discussions on CSI measurement enhancement for AI/ML communication |
TCL |
| R1-2309872 |
Varying CSI feedback granularity based on channel conditions |
Rakuten Symphony |
| R1-2309912 |
Remaining issues on CSI measurement enhancements via AI/ML |
Sony |
| R1-2309931 |
Other aspects on AI/ML for CSI feedback enhancement |
ITL |
| R1-2309952 |
Further aspects of AI/ML for CSI feedback |
Lenovo |
| R1-2309956 |
Discussion on AI/ML for CSI feedback enhancement |
InterDigital, Inc. |
| R1-2309997 |
Other aspects on AI/ML for CSI feedback enhancement |
MediaTek Inc. |
| R1-2310053 |
Discussion on AI/ML for CSI feedback enhancement |
NTT DOCOMO, INC. |
| R1-2310081 |
Discussion on AI/ML for CSI feedback enhancement |
AT&T |
| R1-2310164 |
Other aspects on AI/ML for CSI feedback enhancement |
Qualcomm Incorporated |
| R1-2310185 |
Other aspects on AI/ML for CSI feedback enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2310238 |
Discussions on Other Aspects on AI/ML for CSI Feedback Enhancement |
Indian Institute of Tech (M), IIT Kanpur, CEWiT |
| R1-2310312 |
Summary #1 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2310313 |
Summary #2 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2310314 |
Summary #3 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2310315 |
Summary #4 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2310316 |
Summary #5 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2310317 |
Final summary on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| 8.14.3 |
Remaining aspects on AI/ML |
|
| R1-2308838 |
Remaining Aspects of AI/ML for Positioning Accuracy Enhancement |
Ericsson |
| R1-2308917 |
Highlights for the evaluation on AI/ML based CSI feedback enhancement |
Huawei, HiSilicon |
| R1-2308950 |
Remaining open aspects of AI/ML positioning |
vivo |
| R1-2309398 |
Remaining aspects for evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2309619 |
Other aspects on AI/ML for beam management |
OPPO |
| R1-2310364 |
Summary #1 on Remaining Aspects of Evaluating AI/ML for Positioning Accuracy Enhancement |
Moderator (Ericsson) |
| R1-2310365 |
Summary #2 on Remaining Aspects of Evaluating AI/ML for Positioning Accuracy Enhancement |
Moderator (Ericsson) |
| R1-2310366 |
Summary #3 on Remaining Aspects of Evaluating AI/ML for Positioning Accuracy Enhancement |
Moderator (Ericsson) |
| R1-2310403 |
FL summary #1 on remaining open aspects of AI/ML positioning |
Moderator (vivo) |
| R1-2310416 |
Summary#1 for other aspects on AI/ML for beam management |
Moderator (OPPO) |
| R1-2310417 |
Summary#2 for other aspects on AI/ML for beam management |
Moderator (OPPO) |
| R1-2310442 |
FL summary #1 for remaining aspects for evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2310443 |
FL summary #2 for remaining aspects for evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2310449 |
Summary#1 for CSI evaluation of [114bis-R18-AI/ML] |
Moderator (Huawei) |
| R1-2310450 |
Summary#2 for CSI evaluation of [114bis-R18-AI/ML] |
Moderator (Huawei) |
| R1-2310451 |
Summary#3 for CSI evaluation of [114bis-R18-AI/ML] |
Moderator (Huawei) |
| R1-2310487 |
Summary #4 on Remaining Aspects of Evaluating AI/ML for Positioning Accuracy Enhancement |
Moderator (Ericsson) |
| R1-2310488 |
Summary #5 on Remaining Aspects of Evaluating AI/ML for Positioning Accuracy Enhancement |
Moderator (Ericsson) |
| R1-2310656 |
FL summary #3 for remaining aspects for evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2310657 |
FL summary #4 for remaining aspects for evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2310686 |
Summary#4 for CSI evaluation of [114bis-R18-AI/ML] |
Moderator (Huawei) |
| 8.15 |
Study on Self-Evaluation towards the IMT-2020 Submission of the 3GPP Satellite Radio Interface Technology |
|
| R1-2310547 |
Session notes for 8.15 (Study on Self-Evaluation towards the 3GPP submission of a IMT-2020 Satellite Radio Interface Technology) |
Ad-Hoc Chair (Huawei) |
| 8.15.1 |
Evaluation methodology |
|
| R1-2308902 |
Evaluation methodology of IMT-2020 satellite |
Huawei, HiSilicon |
| R1-2309153 |
Discussion on the evaluation methodology of the self-evaluation |
ZTE |
| R1-2309399 |
Discussion on remaining issues for evaluation methodology |
Samsung |
| R1-2309607 |
Discussion on self-evaluation methodology for IMT-2020 satellite radio interface |
OPPO |
| R1-2309984 |
Evaluation assumptions for HRC-s for IoT NTN |
MediaTek Inc. |
| R1-2310165 |
Further discussion on self-evaluation assumptions |
Qualcomm Incorporated |
| R1-2310358 |
Evaluation methodology of IMT-2020 satellite |
Huawei, HiSilicon |
| R1-2310471 |
Feature lead summary on Evaluation Methodology for IMT-2020 satellite |
Moderator (Qualcomm Incorporated) |
| R1-2310587 |
Feature lead summary#2 on Evaluation Methodology for IMT-2020 satellite |
Moderator (Qualcomm Incorporated) |
| 8.15.2 |
Self-evaluation results for NR NTN |
|
| R1-2308868 |
Self-evaluation results for NR NTN |
THALES |
| R1-2308869 |
Feature Lead Summary#1 on self-evaluation results for NR NTN |
THALES |
| R1-2308870 |
Feature Lead Summary#2 on self-evaluation results for NR NTN |
THALES |
| R1-2308871 |
Feature Lead Summary#3 on self-evaluation results for NR NTN |
THALES |
| R1-2308903 |
Self-evaluation results for NR NTN |
Huawei, HiSilicon |
| R1-2309095 |
Discussions on self evaluation results for NR NTN |
vivo |
| R1-2309154 |
Discussion on the Self-evaluation results for NR NTN |
ZTE |
| R1-2309292 |
Initial results on NR-NTN self evaluation towards IMT 2020 submission |
CEWiT |
| R1-2309400 |
Discussion on evaluation results for NR NTN |
Samsung |
| R1-2309439 |
Self-evaluation results for NR NTN |
xiaomi |
| R1-2309509 |
Further evaluation for NR NTN |
CATT |
| R1-2309608 |
Self-evaluation results for NR NTN |
OPPO |
| R1-2309713 |
Evaluation results on NR-NTN for self-evaluation of IMT-2020 satellite radio interface technology |
Panasonic |
| R1-2309738 |
Evaluation results related to IMT-2020 Satellite for NR over NTN for Earth Fixed Cell |
Nokia, Nokia Shanghai Bell |
| R1-2309944 |
Self-evaluation results for NR NTN |
CCU, ITRI |
| R1-2310054 |
Calibration results and peak data rate analysis for NR NTN |
NTT DOCOMO, INC. |
| R1-2310166 |
Self-evaluation results for NR NTN |
Qualcomm Incorporated |
| R1-2310189 |
Study on Self-Evaluation of Satellite RIT – Energy Efficiency |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2310220 |
Satellite IMT-2020 self-evaluation results for NR NTN |
Ericsson |
| R1-2310222 |
Self-Evaluation Results for NR NTN (Target SNR for target BLER) |
Fraunhofer IIS |
| R1-2310391 |
Self-evaluation results for NR NTN |
Qualcomm Incorporated |
| R1-2310497 |
Further evaluation for NR NTN |
CATT |
| R1-2310558 |
Self-evaluation results for NR NTN |
xiaomi |
| 8.15.3 |
Self-evaluation results for IoT NTN |
|
| R1-2308904 |
Self-evaluation results for IoT NTN |
Huawei, HiSilicon |
| R1-2309155 |
Discussion on the Self-evaluation results for IoT NTN |
ZTE |
| R1-2309609 |
Self-evaluation results for IoT NTN |
OPPO |
| R1-2309985 |
Evaluation results for IoT NTN |
MediaTek Inc. |
| R1-2310167 |
Self-evaluation results for IOT NTN |
Qualcomm Incorporated |
| R1-2310321 |
Evaluation results for IoT NTN |
MediaTek Inc. |
| R1-2310392 |
Self-evaluation results for IOT NTN |
Qualcomm Incorporated |
| R1-2310500 |
Feature Lead summary for 8.15.3: Self-Evaluation Results for IoT NTN |
Moderator (MediaTek) |
| 8.16 |
UE Features |
|
| R1-2310632 |
Updated RAN1 UE features list for Rel-18 LTE after RAN1#114bis |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2310633 |
Draft LS on Rel-18 RAN1 UE features list for LTE after RAN1#114bis |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2310634 |
LS on Rel-18 RAN1 UE features list for LTE after RAN1#114bis |
RAN1, AT&T, NTT DOCOMO, INC. |
| R1-2310635 |
Updated RAN1 UE features list for Rel-18 NR after RAN1#114bis |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2310636 |
Draft LS on Rel-18 RAN1 UE features list for NR after RAN1#114bis |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2310637 |
LS on Rel-18 RAN1 UE features list for NR after RAN1#114bis |
RAN1, AT&T, NTT DOCOMO, INC. |
| 8.16.1 |
UE features for NR MIMO evolution |
|
| R1-2308846 |
On UE features for Rel. 18 MIMO evolution WI |
Nokia, Nokia Shanghai Bell |
| R1-2308930 |
UE features for NR MIMO evolution |
Huawei, HiSilicon |
| R1-2309004 |
Discussion on UE features for NR MIMO evolution |
Spreadtrum Communications |
| R1-2309022 |
Discussion on UE features for NR MIMO evolution |
ZTE |
| R1-2309096 |
Discussion on Rel-18 MIMO UE features |
vivo |
| R1-2309108 |
UE feature for MIMO evolution |
TCL |
| R1-2309169 |
Discussion on Rel-18 MIMO UE features |
LG Electronics |
| R1-2309205 |
UE features for NR-MIMO evolution |
Intel Coporation |
| R1-2309210 |
Discussion on UE features for Rel18 MIMO |
Ericsson |
| R1-2309263 |
UE feature on NR MIMO evolution |
Google |
| R1-2309401 |
UE features for Rel-18 MIMO |
Samsung |
| R1-2309440 |
Discussion on UE features for NR MIMO evolution |
xiaomi |
| R1-2309510 |
Discussion on UE features for NR MIMO evolution |
CATT |
| R1-2309570 |
UE features for Rel-18 MIMO evolution |
OPPO |
| R1-2309645 |
Discussion on UE features for NR MIMO evolution |
Fujitsu |
| R1-2309691 |
UE features for NR MIMO evolution |
CMCC |
| R1-2309856 |
Views on UE features for Rel-18 NR MIMO evolution |
Apple |
| R1-2309880 |
UE Features for NR MIMO Evolution regarding STxMP |
ASUSTeK |
| R1-2309998 |
UE Features for NR MIMO Evolution |
MediaTek Inc. |
| R1-2310055 |
Discussion on UE features for NR MIMO evolution |
NTT DOCOMO, INC. |
| R1-2310072 |
Summary of UE features for NR MIMO evolution |
Moderator (AT&T) |
| R1-2310168 |
UE features for NR MIMO evolution |
Qualcomm Incorporated |
| R1-2310381 |
Session Notes of AI 8.16.1 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| 8.16.2 |
UE features for NR sidelink evolution |
|
| R1-2308847 |
On UE features for NR sidelink evolution |
Nokia, Nokia Shanghai Bell |
| R1-2308887 |
UE features for NR sidelink evolution |
Huawei, HiSilicon |
| R1-2309005 |
Discussion on UE features for NR sidelink evolution |
Spreadtrum Communications |
| R1-2309097 |
Discussion on Rel-18 sidelink UE features |
vivo |
| R1-2309116 |
Discussion on UE features for NR sidelink evolution |
ZTE, Sanechips |
| R1-2309402 |
UE features for NR sidelink evolution |
Samsung |
| R1-2309445 |
Discussion on UE features for NR sidelink evolution |
xiaomi |
| R1-2309513 |
Further discussion on UE features for NR sidelink evolution |
CATT, CICTCI |
| R1-2309626 |
UE features list for Rel-18 NR sidelink evolution WI |
OPPO, Huawei, HiSilicon, LG Electronics |
| R1-2309779 |
Discussion on Rel-18 NR sidelink evolution UE features |
TOYOTA InfoTechnology Center, Hyundai Motor Company, Continental Automotive, Fraunhofer HHI, Fraunhofer IIS |
| R1-2309857 |
On UE Features for Rel-18 NR Sidelink Evolution |
Apple |
| R1-2309996 |
Discussion on UE feature list for NR Sidelink Evolution |
MediaTek Inc. |
| R1-2310056 |
Discussion on UE features for NR SL evolution |
NTT DOCOMO, INC. |
| R1-2310169 |
UE features for NR Rel-18 Sidelink |
Qualcomm Incorporated |
| R1-2310616 |
Summary on UE features for NR sidelink evolution |
Moderator (NTT DOCOMO, INC.) |
| R1-2310624 |
Session Notes for 8.16.2 |
Ad-Hoc Chair (NTT DOCOMO) |
| 8.16.3 |
UE features for expanded and improved NR positioning |
|
| R1-2308848 |
On UE features for expanded and improved NR positioning |
Nokia, Nokia Shanghai Bell |
| R1-2308881 |
UE features for Rel-18 positioning |
Huawei, HiSilicon |
| R1-2309006 |
Discussion on UE features for expanded and improved NR positioning |
Spreadtrum Communications |
| R1-2309098 |
Discussion on Rel-18 positioning UE features |
vivo |
| R1-2309201 |
On UE features for expanded and improved NR positioning |
Intel Coporation |
| R1-2309226 |
Remaining issues on UE feature for Rel-18 NR positioning |
ZTE |
| R1-2309403 |
UE features for expanded and improved NR positioning |
Samsung |
| R1-2309446 |
Discussion on UE features for expanded and improved NR positioning |
xiaomi |
| R1-2309514 |
Further discussion on UE features for expanded and improved NR positioning |
CATT |
| R1-2309625 |
Discussion on UE features for expanded and improved NR positioning |
OPPO |
| R1-2309692 |
Discussion on UE features for expanded and improved NR positioning |
CMCC |
| R1-2309858 |
On UE features for expanded and improved NR positioning |
Apple |
| R1-2310057 |
Discussion on UE features for expanded and improved NR positioning |
NTT DOCOMO, INC. |
| R1-2310073 |
Summary of UE features for expanded and improved NR positioning |
Moderator (AT&T) |
| R1-2310170 |
UE features for NR Rel-18 Positioning |
Qualcomm Incorporated |
| R1-2310202 |
UE features for expanded and improved NR positioning |
Ericsson |
| R1-2310382 |
Session Notes of AI 8.16.3 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| 8.16.4 |
UE features for eRedCap |
|
| R1-2308849 |
On UE features for eRedCap |
Nokia, Nokia Shanghai Bell |
| R1-2308940 |
Discussion on R18 RedCap UE features |
FUTUREWEI |
| R1-2309099 |
Discussion on Rel-18 eRedCap UE features |
vivo |
| R1-2309181 |
Discussion on UE features for eRedcap |
ZTE, Sanechips |
| R1-2309404 |
UE features for eRedCap |
Samsung |
| R1-2309447 |
Discussion on UE features for eRedCap |
xiaomi |
| R1-2309615 |
Rel-18 eRedCap UE features |
OPPO |
| R1-2309859 |
UE features for eRedCap |
Apple |
| R1-2309878 |
UE Feature for Rel-18 RedCap UE |
NEC |
| R1-2309976 |
UE features for eRedCap |
MediaTek Inc. |
| R1-2310058 |
Discussion on UE features for eRedCap |
NTT DOCOMO, INC. |
| R1-2310171 |
UE Features for eRedCap |
Qualcomm Incorporated |
| R1-2310225 |
Cleanup of UE feature list for eRedCap |
Ericsson |
| R1-2310261 |
UE features for Rel-18 RedCap |
Huawei, HiSilicon |
| R1-2310617 |
Summary on UE features for eRedCap |
Moderator (NTT DOCOMO, INC.) |
| R1-2310625 |
Session Notes for 8.16.4 |
Ad-Hoc Chair (NTT DOCOMO) |
| 8.16.5 |
UE features for NR network energy savings |
|
| R1-2308850 |
On UE features for NR network energy savings |
Nokia, Nokia Shanghai Bell |
| R1-2308895 |
UE features for Rel-18 NES |
Huawei, HiSilicon |
| R1-2309100 |
Discussions on Rel-18 network energy saving UE features |
vivo |
| R1-2309182 |
Discussion on UE features for NES |
ZTE, Sanechips |
| R1-2309191 |
Discussion on UE features for NES |
Intel Coporation |
| R1-2309264 |
UE feature on Network Energy Saving |
Google |
| R1-2309308 |
Discussion on UE features for NES |
LG Electronics |
| R1-2309405 |
UE features for NR network energy savings |
Samsung |
| R1-2309448 |
Views on Rel-18 network energy saving UE features |
xiaomi |
| R1-2309515 |
Discussion on Rel-18 UE features for Network Energy Saving |
CATT |
| R1-2309559 |
Discussion on UE features for Network Energy Saving |
China Telecom |
| R1-2309604 |
Discussion on UE features for NR network energy savings |
OPPO |
| R1-2309693 |
Discussion on UE features for network energy saving |
CMCC |
| R1-2309860 |
On UE features for NR network energy savings |
Apple |
| R1-2309930 |
UE Features for Cell DTX/DRX |
Vodafone |
| R1-2310006 |
UE features for NR network energy savings |
MediaTek Inc. |
| R1-2310059 |
Discussion on UE features for NR NW energy savings |
NTT DOCOMO, INC. |
| R1-2310074 |
Summary of UE features for NR network energy savings |
Moderator (AT&T) |
| R1-2310098 |
UE features for Rel-18 network energy savings |
Ericsson |
| R1-2310172 |
UE features for NES |
Qualcomm Incorporated |
| R1-2310383 |
Session Notes of AI 8.16.5 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| 8.16.6 |
UE features for XR enhancements |
|
| R1-2308851 |
On UE features for XR enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2308883 |
UE features for XR enhancements |
Huawei, HiSilicon |
| R1-2309008 |
Discussion on UE features for XR Enhancements |
Spreadtrum Communications |
| R1-2309101 |
Discussion on Rel-18 XR UE features |
vivo |
| R1-2309183 |
Discussion on UE features for XR enhancements |
ZTE, Sanechips |
| R1-2309309 |
Discussion on UE features for XR enhancements |
LG Electronics |
| R1-2309406 |
UE features for XR |
Samsung |
| R1-2309449 |
Discussion on UE features for XR-specific capacity enhancements |
xiaomi |
| R1-2309516 |
Discussion on Rel-18 UE features for XR in RAN1 |
CATT |
| R1-2309628 |
Discussion on UE features for XR |
OPPO |
| R1-2309861 |
UE features for XR enhancements |
Apple |
| R1-2310004 |
Discussion on UE features for XR enhancements |
MediaTek Inc. |
| R1-2310060 |
Discussion on UE features for Rel-18 XR enhancements |
NTT DOCOMO, INC. |
| R1-2310173 |
UE features for XR enhancements |
Qualcomm Incorporated |
| R1-2310256 |
On UE features for XR Enhancements |
Ericsson |
| R1-2310618 |
Summary on UE features for XR enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2310626 |
Session Notes for 8.16.6 |
Ad-Hoc Chair (NTT DOCOMO) |
| 8.16.7 |
UE features for NR mobility enhancements |
|
| R1-2308852 |
On UE features for NR mobility enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2308891 |
UE features on R18 Mobility Enhancement |
Huawei, HiSilicon |
| R1-2309009 |
Discussion on UE features for mobility |
Spreadtrum Communications |
| R1-2309023 |
Discussion on UE features for NR mobility enhancements |
ZTE |
| R1-2309102 |
Discussion on Rel-18 NR mobility enhancements UE features |
vivo |
| R1-2309407 |
UE features for mobility |
Samsung |
| R1-2309450 |
Discussion on the UE features for NR Mobility |
xiaomi |
| R1-2309517 |
On UE features for NR mobility |
CATT |
| R1-2309581 |
Discussion on UE features for NR mobility enhancements |
OPPO |
| R1-2309777 |
UE-features for NR mobility enhancements |
Ericsson |
| R1-2309862 |
UE features for NR mobility enhancements |
Apple |
| R1-2309983 |
Views on UE features for NR mobility enhancements |
MediaTek Inc. |
| R1-2310061 |
Discussion on UE features for NR mobility enhancements |
NTT DOCOMO, INC. |
| R1-2310077 |
Summary of UE features for NR mobility enhancements |
Moderator (AT&T) |
| R1-2310174 |
UE features for NR mobility enhancements |
Qualcomm Incorporated |
| R1-2310384 |
Session Notes of AI 8.16.7 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| 8.16.8 |
UE features for coverage enhancements |
|
| R1-2308853 |
On UE features for coverage enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2309010 |
Discussion on UE features for coverage enhancements |
Spreadtrum Communications |
| R1-2309103 |
Discussions on Rel-18 NR coverage enhancements UE features |
vivo |
| R1-2309138 |
Discussion on UE feature for coverage enhancements |
ZTE |
| R1-2309190 |
Discussion on UE features for NR coverage enhancement |
Intel Coporation |
| R1-2309408 |
UE features for coverage enhancements |
Samsung |
| R1-2309451 |
Discussion on UE features for coverage enhancements |
xiaomi |
| R1-2309518 |
UE features for coverage enhancements |
CATT |
| R1-2309560 |
Discussion on UE features for coverage enhancement |
China Telecom |
| R1-2309616 |
Rel-18 UE features for coverage enhancements |
OPPO |
| R1-2309632 |
Discussion on UE features for further NR coverage enhancement in Rel.18 |
Panasonic |
| R1-2309694 |
Discussion on UE feature for coverage enhancement |
CMCC |
| R1-2309748 |
UE features for Coverage Enhancement |
Huawei, HiSilicon |
| R1-2309863 |
Views on UE features for Rel-18 NR coverage enhancements |
Apple |
| R1-2309970 |
UE Features for Coverage Enhancements |
Ericsson |
| R1-2310003 |
Discussion on UE features for coverage enhancements |
MediaTek Inc. |
| R1-2310062 |
Discussion on UE features for NR further coverage enhancements |
NTT DOCOMO, INC. |
| R1-2310110 |
UE features for Rel-18 Coverage Enhancements |
Sharp |
| R1-2310175 |
UE features for coverage enhancements |
Qualcomm Incorporated |
| R1-2310619 |
Summary on UE features for coverage enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2310627 |
Session Notes for 8.16.8 |
Ad-Hoc Chair (NTT DOCOMO) |
| 8.16.9 |
UE features for dedicated spectrum less than 5MHz |
|
| R1-2308854 |
On UE features for dedicated spectrum less than 5MHz |
Nokia, Nokia Shanghai Bell |
| R1-2308898 |
UE features for dedicated spectrum less than 5MHz |
Huawei, HiSilicon |
| R1-2308942 |
Discussion on less than 5 MHz dedicated spectrum UE features |
FUTUREWEI |
| R1-2309139 |
Discussion on UE feature for dedicated spectrum less than 5MHz |
ZTE |
| R1-2309409 |
UE features for dedicated spectrum less than 5MHz |
Samsung |
| R1-2309864 |
On UE features for Less Than 5MHz FR1 |
Apple |
| R1-2309891 |
On UE features for LessThan5MHzFR1 |
Ericsson |
| R1-2309977 |
UE features for dedicated spectrum less than 5MHz |
MediaTek Inc. |
| R1-2310063 |
Discussion on UE features for dedicated spectrum less than 5MHz |
NTT DOCOMO, INC. |
| R1-2310176 |
UE features for dedicated spectrum less than 5MHz |
Qualcomm Incorporated |
| R1-2310620 |
Summary on UE features for dedicated spectrum less than 5MHz |
Moderator (NTT DOCOMO, INC.) |
| R1-2310628 |
Session Notes for 8.16.9 |
Ad-Hoc Chair (NTT DOCOMO) |
| 8.16.10 |
UE features for eDSS |
|
| R1-2308855 |
On UE features for eDSS |
Nokia, Nokia Shanghai Bell |
| R1-2308921 |
UE features for eDSS |
Huawei, HiSilicon |
| R1-2309140 |
Discussion on UE feature for eDSS |
ZTE |
| R1-2309629 |
Discussion on UE features for eDSS |
OPPO |
| R1-2310064 |
Discussion on UE features for eDSS |
NTT DOCOMO, INC. |
| R1-2310099 |
UE features for Rel18 DSS Enhancements |
Ericsson |
| R1-2310177 |
UE features for eDSS |
Qualcomm Incorporated |
| R1-2310621 |
Summary on UE features for eDSS |
Moderator (NTT DOCOMO, INC.) |
| R1-2310629 |
Session Notes for 8.16.10 |
Ad-Hoc Chair (NTT DOCOMO) |
| 8.16.11 |
UE features for NR NCR |
|
| R1-2308856 |
On UE features for NR NCR |
Nokia, Nokia Shanghai Bell |
| R1-2308907 |
UE features for NR NCR |
Huawei, HiSilicon |
| R1-2309104 |
Discussion on Rel-18 NCR UE features |
vivo |
| R1-2309156 |
Discussion on UE features for NCR |
ZTE |
| R1-2309332 |
Discussion on UE features for NR NCR |
LG Electronics |
| R1-2309410 |
UE features for NR NCR |
Samsung |
| R1-2309441 |
Discussion on UE features for NR NCR |
xiaomi |
| R1-2309511 |
Further discussion on UE features for NR network-Controlled Repeaters |
CATT |
| R1-2309561 |
Discussion on UE features for NCR |
China Telecom |
| R1-2309646 |
Discussion on UE features for NR NCR |
Fujitsu |
| R1-2309695 |
Discussion on UE feature for NR NCR |
CMCC |
| R1-2309711 |
Discussion on NCR features |
ETRI |
| R1-2309776 |
UE-features for NCR |
Ericsson |
| R1-2309913 |
Remaining issues on UE features for NR NCR |
Sony |
| R1-2310065 |
Discussion on UE features for NR NCR |
NTT DOCOMO, INC. |
| R1-2310075 |
Summary of UE features for NR NCR |
Moderator (AT&T) |
| R1-2310385 |
Session Notes of AI 8.16.11 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| 8.16.12 |
UE features for MC enhancements |
|
| R1-2308857 |
On UE features for MC enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2308918 |
Discussion on UE features for MC enhancements |
Huawei, HiSilicon |
| R1-2309011 |
Discussion on UE features for multi-carrier enhancement |
Spreadtrum Communications |
| R1-2309105 |
Discussion on Rel-18 Multi-carrier enhancements UE features |
vivo |
| R1-2309141 |
Discussion on UE feature for MC enhancements |
ZTE |
| R1-2309310 |
Discussion on UE features for MC enhancements |
LG Electronics |
| R1-2309411 |
UE features for multi-carrier enhancements |
Samsung |
| R1-2309442 |
Discussion on UE features for MC enhancements |
xiaomi |
| R1-2309512 |
Further discussion on UE features for MC enhancements |
CATT |
| R1-2309627 |
Discussion on UE features for multi-carrier enhancement |
OPPO |
| R1-2309865 |
Views on UE features for Rel-18 MC enhancements |
Apple |
| R1-2309973 |
On UE feature discussion for Rel-18 multi-carrier enhancement |
MediaTek Inc. |
| R1-2310066 |
Discussion on UE features for Multi-carrier enhancements |
NTT DOCOMO, INC. |
| R1-2310100 |
UE features for Rel-18 multi-carrier enhancements |
Ericsson |
| R1-2310178 |
UE features for MC enhancements |
Qualcomm Incorporated |
| R1-2310622 |
Summary on UE features for MC enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2310630 |
Session Notes for 8.16.12 |
Ad-Hoc Chair (NTT DOCOMO) |
| 8.16.13 |
UE features for IoT NTN enhancements |
|
| R1-2308858 |
On UE features for IoT NTN enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2308914 |
UE features for IoT NTN enhancements |
Huawei, HiSilicon |
| R1-2309012 |
Discussion on UE features for IoT NTN enhancements |
Spreadtrum Communications |
| R1-2309157 |
Discussion on UE features for IoT-NTN |
ZTE |
| R1-2309412 |
UE features for IoT NTN enhancements |
Samsung |
| R1-2309443 |
Discussion on the UE features for IoT NTN |
xiaomi |
| R1-2309605 |
Discussion on UE features for IoT NTN enhancements |
OPPO |
| R1-2309866 |
On UE Features for Rel-18 IoT NTN Enhancements |
Apple |
| R1-2309890 |
On UE features for IoT NTN enhancements |
Ericsson |
| R1-2309981 |
Views on UE features for Rel-18 IoT NTN enhancements |
MediaTek Inc. |
| R1-2310078 |
Summary of UE features for IoT NTN enhancements |
Moderator (AT&T) |
| R1-2310179 |
UE features for IOT NTN enhancements |
Qualcomm Incorporated |
| R1-2310386 |
Session Notes of AI 8.16.13 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| 8.16.14 |
UE features for NR NTN enhancements |
|
| R1-2308859 |
On UE features for NR NTN enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2308913 |
UE features for NR NTN enhancements |
Huawei, HiSilicon |
| R1-2309007 |
Discussion on UE features for NR NTN enhancements |
Spreadtrum Communications |
| R1-2309106 |
Discussions on NR NTN enhancements UE features |
vivo |
| R1-2309158 |
Discussion on UE features for NR-NTN |
ZTE |
| R1-2309251 |
UE features for NR NTN enhancements |
Baicells |
| R1-2309314 |
On UE features for NR NTN enhancements |
Ericsson |
| R1-2309335 |
Discussions on UE features for NR NTN enhancements |
LG Electronics |
| R1-2309413 |
UE features for NR NTN enhancements |
Samsung |
| R1-2309444 |
Discussion on the UE features for NR NTN |
xiaomi |
| R1-2309549 |
UE features for NR NTN enhancements |
NEC |
| R1-2309606 |
Discussion on UE features for NR NTN enhancements |
OPPO |
| R1-2309867 |
On UE Features for Rel-18 NR NTN Enhancements |
Apple |
| R1-2310067 |
Discussion on UE features for NR NTN enhancements |
NTT DOCOMO, INC. |
| R1-2310076 |
Summary of UE features for NR NTN enhancements |
Moderator (AT&T) |
| R1-2310111 |
Discussions on UE features for NR NTN |
Sharp |
| R1-2310180 |
UE features for NR NTN enhancements |
Qualcomm Incorporated |
| R1-2310387 |
Session Notes of AI 8.16.14 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| 8.16.15 |
UE features for BWP without restriction |
|
| R1-2308860 |
On UE features for BWP without restriction |
Nokia, Nokia Shanghai Bell |
| R1-2309414 |
UE features for BWP without restriction |
Samsung |
| R1-2309929 |
Miscellaneous issues on BWP Without Restriction |
Vodafone, vivo, Nokia |
| R1-2310005 |
UE features for BWP without restriction |
MediaTek Inc. |
| R1-2310079 |
Summary of UE features for BWP without restriction |
Moderator (AT&T) |
| R1-2310242 |
UE features for BWP without restriction |
Ericsson |
| R1-2310388 |
Session Notes of AI 8.16.15 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| 8.16.16 |
Other |
|
| R1-2308861 |
On UE features for TEI18 |
Nokia, Nokia Shanghai Bell |
| R1-2308888 |
UE features for endorsed Rel-18 TEI on HARQ multiplexing on PUSCH |
Huawei, HiSilicon |
| R1-2309142 |
Discussion on UE feature for Rel-18 TEI |
ZTE |
| R1-2309415 |
UE features for endorsed Rel-18 TEI |
Samsung |
| R1-2310181 |
Other UE features including TEI and span-based PDCCH monitoring with additional restrictions |
Qualcomm Incorporated |
| R1-2310623 |
Summary on UE features for TEIs |
Moderator (NTT DOCOMO, INC.) |
| R1-2310631 |
Session Notes for 8.16.16 |
Ad-Hoc Chair (NTT DOCOMO) |
| 8.17 |
Other |
|
| R1-2309416 |
Remaining issue for HARQ-ACK multiplexing on PUSCH |
Samsung |
| R1-2309696 |
TP for TR 38.858 Study on Evolution of NR Duplex Operation |
CMCC, Samsung |
| R1-2309697 |
TR38.869 v 1.1.0 Study on low-power wake up signal and receiver for NR |
CMCC, vivo |
| R1-2310182 |
Maintenance for BWP without restriction |
Qualcomm Incorporated |
| R1-2310513 |
Summary of discussion on multiplexing HARQ-ACK in a PUSCH |
Moderator (Samsung) |
| R1-2310519 |
TP for TR 38.858 Study on Evolution of NR Duplex Operation |
CMCC, Samsung |
| R1-2310553 |
TR38.869 v 1.1.0 Study on low-power wake up signal and receiver for NR |
CMCC, vivo |
| R1-2310652 |
TR38.869 v 1.1.0 Study on low-power wake up signal and receiver for NR |
CMCC, vivo |
| R1-2310773 |
TR38.869 v 1.1.1 Study on low-power wake up signal and receiver for NR |
CMCC, vivo |